CVE-2026-24708: An issue was discovered in OpenStack Nova before 30.2.2, 31 before 31.2.1, and 32 before 32.1.1.
An issue was discovered in OpenStack Nova before 30.2.2, 31 before 31.2.1, and 32 before 32.1.1. By writing a malicious QCOW header to a root or ephemeral disk and then triggering a resize, a user may convince Nova's Flat image backend to call qemu-img without a format restriction, resulting in an unsafe image resize operation that could destroy data on the host system. Only compute nodes using the Flat image backend (usually configured with use_cow_images=False) are affected.
Security readout for executives and security teams
Plain-English summary
This Nova flaw can let an authenticated cloud user trigger an unsafe disk resize path that may destroy data on an OpenStack compute host. The risk is concentrated in deployments using Nova's Flat image backend, commonly with use_cow_images=False, and affected Nova releases before the listed fixed versions.
Executive priority
Treat this as a high-priority cloud infrastructure issue if your OpenStack estate uses Nova Flat image backend. The business concern is possible host-level data loss from a tenant-accessible path, not broad internet unauthenticated compromise.
Technical view
Nova's Flat image backend can invoke qemu-img for resize without enforcing an image format restriction after crafted QCOW metadata is placed on a root or ephemeral disk. The reported impact is host data destruction. Affected versions are before 30.2.2, 31.2.1, and 32.1.1.
Likely exposure
Exposure is likely limited to OpenStack Nova compute nodes using the Flat image backend, usually configured with use_cow_images=False. Other image backends are not identified as affected in the source bundle.
Exploitation context
The CVSS vector indicates low privileges are required, user interaction is not required, and attack complexity is high. The bundle does not show CISA KEV listing or cited evidence of active exploitation.
Researcher notes
Key scoping details are backend-specific exposure, fixed upstream versions, and high attack complexity. The provided evidence does not establish active exploitation. Validate backend configuration before declaring broad OpenStack exposure.
Mitigation direction
Upgrade Nova to 30.2.2, 31.2.1, 32.1.1, or later as applicable.
Review OpenStack, Debian, and Red Hat advisories for distribution-specific fixes.
Prioritize compute nodes using the Flat image backend or use_cow_images=False.
Check vendor guidance before applying compensating controls not named in advisories.
Validation and detection
Inventory Nova versions across controllers and compute nodes.
Identify compute nodes configured for the Flat image backend.
Confirm whether use_cow_images=False is present in Nova configuration.
Review recent resize activity on exposed compute nodes for abnormal failures or host data impact.
Verify package updates against Debian or Red Hat advisory status where applicable.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-669: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-669 · source CWE mapping
Incorrect Resource Transfer Between Spheres
Incorrect Resource Transfer Between Spheres represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
External Control of File Name or Path represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.