CVE-2026-48914

MEDIUMPre-NVD 6.76.7—
EchelonGraph scoreMEDIUM confidence

Score 6.7 from GitHub Security Advisory published 2026-06-12. a secondary CVSS source baseline 6.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
6.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.7Exploit: None knownExposed: 0

A fix is available — apply it.

A flaw was found in QEMU's virtio-blk device. The issue arises because the device does not properly validate the size of input descriptors before writing data. A malicious guest with high privileges could exploit this vulnerability by submitting a malformed virtio-blk SCSI request, leading to an out-of-bounds write in the host heap memory and a potential denial of service (DoS) for the QEMU process.

CVSS v3
6.7
EG Score
6.7(medium)
EG Risk
30(Track)
EG Risk 30/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
Severity67% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

June 12, 2026

Last Modified

August 31, 2026

Advisory Details (3)

Auto-updated Jun 12, 2026
Patch available. Sources: redhat.
generic

[PATCH] virtio-blk: add missing VIRTIO_BLK_T_SCSI_CMD size check (CVE-2026-48914) - Stefan Hajnoczi

https://lore.kernel.org/qemu-devel/[email protected]/
redhat

2488283 – (CVE-2026-48914) CVE-2026-48914 qemu-kvm: Heap Buffer Overflow in virtio-blk SCSI Request Handling

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

cve-details

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

Vendor Advisories for CVE-2026-48914(4)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatqemu-kvm-18:10.1.0-16.el10_2.52026-08-24redhat
redhatqemu-kvm-17:10.1.0-17.el9_8.42026-07-14redhat

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
qemu1:10.0.0+ds-1 ... 1:9.2.2+ds-1~bpo12+1 (225 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
qemu1:10.0.0+ds-1 ... 1:9.2.2+ds-1~bpo12+1 (199 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
qemu1:10.0.10+ds-0+deb13u1 ... 1:10.0.8+ds-0+deb13u1 (13 versions)1:10.0.11+ds-0+deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
qemu1:10.0.2+ds-2 ... 1:11.0.1+ds-1 (43 versions)1:11.0.2+ds-1—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-48914?
CVE-2026-48914 is a medium vulnerability published on June 12, 2026. A flaw was found in QEMU's virtio-blk device. The issue arises because the device does not properly validate the size of input descriptors before writing data. A malicious guest with high privileges could exploit this vulnerability by submitting a malformed virtio-blk SCSI request, leading to an…
When was CVE-2026-48914 disclosed?
CVE-2026-48914 was first published in the National Vulnerability Database on June 12, 2026, with the most recent update on August 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48914 actively exploited?
CVE-2026-48914 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 94.6% of all scored CVEs.
What is the CVSS score of CVE-2026-48914?
CVE-2026-48914 has a CVSS v3 base score of 6.7 (NVD).
How do I remediate CVE-2026-48914?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48914, 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-48914

Explore →

Is Your Infrastructure Affected by CVE-2026-48914?

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

Start Free Scan →Browse All CVEs