Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.4amended

OpenStack Nova: Nova scheduler hint injection bypasses Placement resource claims and scheduling constraints

CVE-2026-46448GHSA-mfg3-p6m3-gjgr

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI nova

    Affected
    >= 18.0.0, <= 31.3.0>= 32.0.0, < 32.2.1>= 33.0.0, <= 33.0.1
    Fixed in
    33.0.2, 32.2.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L
EPSS
  • CVE-2026-46448: 0.27% estimated exploitation activity in the next 30 days; percentile 19.61 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Affects - Nova: =18.0.0 <31.3.1, =32.0.0 <32.2.1, =33.0.0 <33.0.2 Description Erichen from the Institute of Computing Technology, Chinese Academy of Sciences reported that Nova's server create API does not strip internal scheduler hints. An authenticated user can bypass Placement resource claims and scheduling constraint enforcement, including availability zone, host aggregate, and image trait restrictions. The resulting instance has no Placement allocation, which can lead to compute node resource exhaustion and cross-tenant data persistence on NVMe devices after instance deletion. Deployments running Nova 18.0.0 or later are affected. Patches - https://review.opendev.org/993604 (2025.1/epoxy) - https://review.opendev.org/993603 (2025.2/flamingo) - https://review.opendev.org/993602 (2026.1/gazpacho) - https://review.opendev.org/993601 (2026.2/hibiscus) Credits - Erichen from Institute of Computing Technology, Chinese Academy of Sciences (CVE-2026-46448)

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-mfg3-p6m3-gjgr

  2. Revision 1 · created ·

    Published from osv record GHSA-mfg3-p6m3-gjgr

Agent brief

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

# Patch Next advisory brief: CVE-2026-46448

Advisory: OpenStack Nova: Nova scheduler hint injection bypasses Placement resource claims and scheduling constraints
IDs: CVE-2026-46448, GHSA-mfg3-p6m3-gjgr
Record: https://patchnext.com/advisories/cve-2026-46448 (revision 2, source checked 26 Oct 2026, 13:49 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: nova 33.0.2, 32.2.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI nova: affected >= 18.0.0, <= 31.3.0; >= 32.0.0, < 32.2.1; >= 33.0.0, <= 33.0.1; fixed in 33.0.2, 32.2.1

## 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-mfg3-p6m3-gjgr (OSV record GHSA-mfg3-p6m3-gjgr lists affected ranges: PyPI nova >=18.0.0 =32.0.0 =33.0.0 <33.0.2 (fixed))
- Verified: https://github.com/advisories/GHSA-mfg3-p6m3-gjgr (GitHub-reviewed advisory GHSA-mfg3-p6m3-gjgr lists affected ranges: PyPI nova >=18.0.0 =32.0.0 =33.0.0 <=33.0.1)

Commands are suggestions: review each one before running it.

Loading voting…