CVE-2026-48914

MEDIUMPre-NVD 6.76.7—
EchelonGraph scoreHIGH confidence

Score 6.7 from GitHub Security Advisory published 2026-06-12. the CNA's CVSS baseline 6.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:redhat, epss, ghsa
Trending — 4 sources updated this week
6.7
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.7Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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(high)
EPSS
2.2%
KEV
Not listed

Published

June 12, 2026

Last Modified

June 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/[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(2)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 21× in last 7d / 94× 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.

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

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 June 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 2.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-48914?
CVE-2026-48914 has a CVSS v4.0 base score of 6.7 (CNA self-assessment; NVD's own analysis pending).
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