OpenStack Compute (Nova) does not verify the virtual size of a QCOW2 image

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.9 · CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2013-2096: 0.39% estimated exploitation activity in the next 30 days; percentile 32.75 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

OpenStack Compute (Nova) Folsom, Grizzly, and Havana does not verify the virtual size of a QCOW2 image, which allows local users to cause a denial of service (host file system disk consumption) by creating an image with a large virtual size that does not contain a large amount of data.

Published by the source

17 May 2022, 04:55 UTC

Last modified by the source

7 Jul 2026, 11:56 UTC

Source last checked

26 Oct 2026, 13:31 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-m674-hmx2-ffhq

2. Revision 2 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-m674-hmx2-ffhq

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2013-2096

Advisory: OpenStack Compute (Nova) does not verify the virtual size of a QCOW2 image
IDs: CVE-2013-2096, GHSA-m674-hmx2-ffhq
Record: https://patchnext.com/advisories/cve-2013-2096 (revision 3, source checked 26 Oct 2026, 13:31 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: nova 12.0.0a0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI nova: affected < 12.0.0a0; fixed in 12.0.0a0

## Suggested inspection (read-only)
- `python -m pip show nova`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on nova.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-m674-hmx2-ffhq (OSV record GHSA-m674-hmx2-ffhq lists affected ranges: PyPI nova >=0 <12.0.0a0 (fixed))
- Verified: https://github.com/advisories/GHSA-m674-hmx2-ffhq (GitHub-reviewed advisory GHSA-m674-hmx2-ffhq lists affected ranges: PyPI nova >=0 <12.0.0a0)

Commands are suggestions: review each one before running it.