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
Trending — 4 sources updated this week
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: NoneExposed: 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

July 15, 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/20260526154957.1741622-1-stefanha@redhat.com/
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(3)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
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.

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same vendor + 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 July 15, 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

Explore the affected products and dependency analysis for 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