CVE-2026-16313

HIGHPre-NVD 7.67.6—
EchelonGraph scoreHIGH 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%CVSS: 7.6Exploit: None knownExposed: 0

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.6(high)
EG Risk
34(Track)
EG Risk 34/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

July 28, 2026

Last Modified

August 18, 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(5)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhcos-4.22.9.8.202608130832-02026-08-18redhat
redhatsg3_utils-0:1.44-6.el8_10.12026-08-18redhat
redhatsg3_utils-0:1.48-7.el10_2.12026-08-04redhat
redhatsg3_utils-0:1.47-10.el9_8.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 rangeFixed inDependents
sg3-utils1.45-1 ... 1.48-3~deb13u1 (9 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
sg3-utils1.46-3 ... 1.48-3~deb13u1 (6 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
sg3-utils1.48-2, 1.48-3, 1.48-3~deb13u1——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
sg3-utils1.48-2, 1.48-3, 1.48-3~deb13u1——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 53× in last 7d / 148× 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 148 total refreshes for this CVE.

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

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 in the National Vulnerability Database on July 28, 2026, with the most recent update on August 18, 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% probability of exploitation in the next 30 days, which ranks it in the top 84.5% of all scored CVEs.
What is the CVSS score of CVE-2026-16313?
CVE-2026-16313 has a CVSS v3 base score of 7.6 (NVD).
How do I remediate CVE-2026-16313?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16313, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs