CVE-2026-2243

MEDIUMNVD 5.15.1
EchelonGraph scoreMEDIUM confidence

Score 5.1 from GitHub Security Advisory published 2026-02-19. NVD baseline CVSS 5.1; sources differ by 0.0.

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

A fix is available — apply it.

A flaw was found in QEMU. A specially crafted VMDK image could trigger an out-of-bounds read vulnerability, potentially leading to a 12-byte leak of sensitive information or a denial of service condition (DoS).

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

Published

February 19, 2026

Last Modified

August 31, 2026

Advisory Details (2)

Auto-updated Aug 9, 2026
Patch available. Sources: redhat.
redhat

2440934 – (CVE-2026-2243) CVE-2026-2243 qemu-kvm: Heap buffer out-of-bounds read in VMDK compressed grain parsing

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

CVE-2026-2243 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuqemu-utils (1:2.5+dfsg-5ubuntu10.51+esm4) @ xenial2026-08-21ubuntu
ubuntuqemu-utils (1:8.2.2+ds-0ubuntu1.16) @ noble2026-08-21ubuntu

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.2+ds-2 ... 1:10.0.8+ds-0+deb13u1 (12 versions)1:10.0.10+ds-0+deb13u1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
qemu1:10.0.2+ds-2 ... 1:10.2.1+ds-1 (31 versions)1:10.2.2+ds-1

Weakness Classification(1)

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

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-2243?
CVE-2026-2243 is a medium vulnerability published on February 19, 2026. A flaw was found in QEMU. A specially crafted VMDK image could trigger an out-of-bounds read vulnerability, potentially leading to a 12-byte leak of sensitive information or a denial of service condition (DoS).
When was CVE-2026-2243 disclosed?
CVE-2026-2243 was first published in the National Vulnerability Database on February 19, 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-2243 actively exploited?
CVE-2026-2243 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 98.0% of all scored CVEs.
What is the CVSS score of CVE-2026-2243?
CVE-2026-2243 has a CVSS v3 base score of 5.1 (NVD).
How do I remediate CVE-2026-2243?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-2243, 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-2243

Explore →

Is Your Infrastructure Affected by CVE-2026-2243?

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