OpenStack Nova vulnerable to unauthorized access to potentially sensitive data

Exploitation

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

CVSS 4.0

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

EPSS

• CVE-2024-40767: 0.95% estimated exploitation activity in the next 30 days; percentile 61.27 (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.

In OpenStack Nova before 27.4.1, 28 before 28.2.1, and 29 before 29.1.1, by supplying a raw format image that is actually a crafted QCOW2 image with a backing file path or VMDK flat image with a descriptor file path, an authenticated user may convince systems to return a copy of the referenced file's contents from the server, resulting in unauthorized access to potentially sensitive data. All Nova deployments are affected. NOTE: this issue exists because of an incomplete fix for CVE-2022-47951 and CVE-2024-32498.

Published by the source

24 Jul 2024, 06:31 UTC

Last modified by the source

7 Jul 2026, 17:56 UTC

Source last checked

26 Oct 2026, 13:35 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-rm86-h44c-2r2m

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-rm86-h44c-2r2m

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

# Patch Next advisory brief: CVE-2024-40767

Advisory: OpenStack Nova vulnerable to unauthorized access to potentially sensitive data
IDs: CVE-2024-40767, GHSA-rm86-h44c-2r2m
Record: https://patchnext.com/advisories/cve-2024-40767 (revision 3, source checked 26 Oct 2026, 13:35 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI nova: affected <= 27.4.0; >= 28.0.0, <= 28.2.0; >= 29.0.0, <= 29.1.0

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

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## 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-rm86-h44c-2r2m (OSV record GHSA-rm86-h44c-2r2m lists affected ranges: PyPI nova >=0 =28.0.0 =29.0.0 <=29.1.0)
- Verified: https://github.com/advisories/GHSA-rm86-h44c-2r2m (GitHub-reviewed advisory GHSA-rm86-h44c-2r2m lists affected ranges: PyPI nova >=0 =28.0.0 =29.0.0 <=29.1.0)

Commands are suggestions: review each one before running it.