CVE-2026-16313

HIGHPre-NVD 7.67.6—
EchelonGraph scoreMEDIUM confidence

Score 7.6 from GitHub Security Advisory (severity: HIGH) published 2026-07-28. A secondary CVSS source baseline 7.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — Patch released this week
7.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw was found in sg3_utils. The sg_inq command, when invoked with the --export option, outputs device identification data without sanitizing control characters in SCSI name string fields. A newline character embedded in a device-supplied name string can inject arbitrary properties into the udev device database. This could allow an attacker who can present a crafted SCSI device to execute arbitrary commands as root when the device is disconnected.

CVSS v3
7.6
EG Score
7.6HIGHmedium confidence
EG Risk
34
EG Risk 34/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity76% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
26th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 28, 2026

Last Modified

October 1, 2026

Advisory Details (3)

Auto-updated Jul 28, 2026
Patch available. Sources: redhat, github_pr.
github_pr

sg_inq: --export output conformance for SCSI name string and ATA fields

Upstream fix in progress (PR #83 · doug-gilbert/sg3_utils, state=open)

https://github.com/doug-gilbert/sg3_utils/pull/83
redhat

Bug Access Denied

https://bugzilla.redhat.com/show_bug.cgi?id=2502845
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-16313

Vendor Advisories for CVE-2026-16313(20)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(19)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhcos-417.94.202609191027-02026-10-01redhat
redhatrhcos-416.94.202609140240-02026-09-24redhat
redhatsg3_utils-0:1.48-7.el10_0.22026-09-21redhat
redhatrhcos-412.86.202609082051-02026-09-17redhat
redhatrhcos-418.94.202609031320-02026-09-17redhat
redhatsg3_utils-1:1.37-20.el7_92026-09-14redhat
redhatrhcos-4.19.9.6.202609021231-02026-09-09redhat
redhatrhcos-4.20.9.6.202609021029-02026-09-08redhat
redhatrhcos-4.21.9.6.202609021100-02026-09-08redhat
redhatsg3_utils-0:1.47-9.el9_2.12026-08-31redhat
redhatsg3_utils-0:1.47-9.el9_4.12026-08-31redhat
redhatsg3_utils-0:1.47-10.el9_6.22026-08-25redhat
redhatsg3_utils-0:1.44-5.el8_6.12026-08-25redhat
redhatsg3_utils-0:1.44-5.el8_4.12026-08-25redhat
redhatsg3_utils-0:1.44-6.el8_8.12026-08-25redhat
redhatsg3_utils-0:1.44-6.el8_10.12026-08-18redhat
redhatrhcos-4.22.9.8.202608130832-02026-08-18redhat
redhatsg3_utils-0:1.47-10.el9_8.12026-08-04redhat
redhatsg3_utils-0:1.48-7.el10_2.12026-08-04redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
sg3-utils1.45-1 ... 1.48-3~deb13u1 (9 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
sg3-utils1.46-3 ... 1.48-3~deb13u1 (6 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
sg3-utils1.48-2, 1.48-3, 1.48-3~deb13u1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
sg3-utils1.48-2, 1.48-3, 1.48-3~deb13u1
  • every version on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 29× in last 7d / 158× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 404 total refreshes for this CVE.

  1. 2026-10-05 02:43 UTCEG score recompute
  2. 2026-10-05 02:43 UTCVendor advisory
  3. 2026-10-05 02:43 UTCGHSA enrichment
  4. 2026-10-04 23:21 UTCEPSS rescore
  5. 2026-10-04 07:09 UTCEG score recompute
  6. 2026-10-04 07:09 UTCVendor advisory
  7. 2026-10-04 07:09 UTCGHSA enrichment
  8. 2026-10-03 14:25 UTCEPSS rescore
  9. 2026-10-02 18:24 UTCEG score recompute
  10. 2026-10-02 18:24 UTCVendor advisory
  11. 2026-10-02 18:24 UTCGHSA enrichment
  12. 2026-10-01 19:49 UTCEPSS rescore
  13. 2026-10-01 17:28 UTCEG score recompute
  14. 2026-10-01 17:28 UTCVendor advisory
  15. 2026-10-01 17:28 UTCGHSA enrichment
  16. 2026-10-01 16:42 UTCEG score recompute
  17. 2026-10-01 16:42 UTCVendor advisory
  18. 2026-10-01 16:42 UTCGHSA enrichment
  19. 2026-10-01 14:54 UTCVendor advisory
  20. 2026-10-01 14:54 UTCGHSA enrichment
  21. 2026-10-01 03:43 UTCEG score recompute
  22. 2026-10-01 03:43 UTCVendor advisory
  23. 2026-10-01 03:43 UTCGHSA enrichment
  24. 2026-09-30 15:02 UTCEPSS rescore
  25. 2026-09-29 15:20 UTCEPSS rescore
Show 75 more
  1. 2026-09-29 07:45 UTCEG score recompute
  2. 2026-09-29 07:45 UTCVendor advisory
  3. 2026-09-29 07:45 UTCGHSA enrichment
  4. 2026-09-28 13:51 UTCEPSS rescore
  5. 2026-09-28 03:22 UTCEG score recompute
  6. 2026-09-28 03:22 UTCVendor advisory
  7. 2026-09-28 03:22 UTCGHSA enrichment
  8. 2026-09-27 13:47 UTCEPSS rescore
  9. 2026-09-26 15:58 UTCEPSS rescore
  10. 2026-09-25 06:12 UTCEG score recompute
  11. 2026-09-25 06:12 UTCVendor advisory
  12. 2026-09-25 06:12 UTCGHSA enrichment
  13. 2026-09-24 12:18 UTCEG score recompute
  14. 2026-09-24 12:18 UTCVendor advisory
  15. 2026-09-24 12:18 UTCGHSA enrichment
  16. 2026-09-24 11:18 UTCEG score recompute
  17. 2026-09-24 11:18 UTCVendor advisory
  18. 2026-09-24 11:18 UTCGHSA enrichment
  19. 2026-09-24 09:06 UTCVendor advisory
  20. 2026-09-24 09:06 UTCGHSA enrichment
  21. 2026-09-23 21:55 UTCEG score recompute
  22. 2026-09-23 21:55 UTCVendor advisory
  23. 2026-09-23 21:55 UTCGHSA enrichment
  24. 2026-09-23 08:53 UTCVendor advisory
  25. 2026-09-23 08:53 UTCGHSA enrichment
  26. 2026-09-22 21:41 UTCEG score recompute
  27. 2026-09-22 21:41 UTCVendor advisory
  28. 2026-09-22 21:41 UTCGHSA enrichment
  29. 2026-09-21 04:22 UTCEG score recompute
  30. 2026-09-21 04:22 UTCVendor advisory
  31. 2026-09-21 04:21 UTCGHSA enrichment
  32. 2026-09-21 03:40 UTCEG score recompute
  33. 2026-09-21 03:40 UTCVendor advisory
  34. 2026-09-21 03:40 UTCGHSA enrichment
  35. 2026-09-20 00:35 UTCEG score recompute
  36. 2026-09-20 00:35 UTCVendor advisory
  37. 2026-09-20 00:35 UTCGHSA enrichment
  38. 2026-09-19 05:16 UTCEG score recompute
  39. 2026-09-19 05:16 UTCVendor advisory
  40. 2026-09-19 05:16 UTCGHSA enrichment
  41. 2026-09-18 19:27 UTCEPSS rescore
  42. 2026-09-18 17:56 UTCVendor advisory
  43. 2026-09-18 17:56 UTCGHSA enrichment
  44. 2026-09-18 02:05 UTCEG score recompute
  45. 2026-09-18 02:05 UTCVendor advisory
  46. 2026-09-18 02:05 UTCGHSA enrichment
  47. 2026-09-17 12:19 UTCEG score recompute
  48. 2026-09-17 12:19 UTCVendor advisory
  49. 2026-09-17 12:19 UTCGHSA enrichment
  50. 2026-09-17 11:49 UTCEG score recompute
  51. 2026-09-17 11:49 UTCVendor advisory
  52. 2026-09-17 11:49 UTCGHSA enrichment
  53. 2026-09-17 08:29 UTCEG score recompute
  54. 2026-09-17 08:29 UTCVendor advisory
  55. 2026-09-17 08:29 UTCGHSA enrichment
  56. 2026-09-17 08:09 UTCEG score recompute
  57. 2026-09-17 08:09 UTCVendor advisory
  58. 2026-09-17 08:09 UTCGHSA enrichment
  59. 2026-09-17 01:40 UTCEG score recompute
  60. 2026-09-17 01:40 UTCVendor advisory
  61. 2026-09-17 01:40 UTCGHSA enrichment
  62. 2026-09-16 14:07 UTCEPSS rescore
  63. 2026-09-16 05:53 UTCEG score recompute
  64. 2026-09-16 05:53 UTCVendor advisory
  65. 2026-09-16 05:53 UTCGHSA enrichment
  66. 2026-09-16 05:14 UTCEPSS rescore
  67. 2026-09-15 08:38 UTCEG score recompute
  68. 2026-09-15 08:38 UTCVendor advisory
  69. 2026-09-15 08:38 UTCGHSA enrichment
  70. 2026-09-14 06:20 UTCEG score recompute
  71. 2026-09-14 06:20 UTCVendor advisory
  72. 2026-09-14 06:20 UTCGHSA enrichment
  73. 2026-09-14 05:30 UTCEG score recompute
  74. 2026-09-14 05:30 UTCVendor advisory
  75. 2026-09-14 05:30 UTCGHSA enrichment

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-16313?
CVE-2026-16313 is a high vulnerability published on July 28, 2026. A flaw was found in sg3utils. The sginq command, when invoked with the --export option, outputs device identification data without sanitizing control characters in SCSI name string fields. A newline character embedded in a device-supplied name string can inject arbitrary properties into the udev…
When was CVE-2026-16313 disclosed?
CVE-2026-16313 was first published on July 28, 2026, with the most recent update on October 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-16313 actively exploited?
CVE-2026-16313 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (26th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-16313?
CVE-2026-16313 has a CVSS base score of 7.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-16313?
A fix for CVE-2026-16313 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-16313 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-16313

Explore →

Is Your Infrastructure Affected by CVE-2026-16313?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs