CVE-2026-46448

HIGHNVD 8.58.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 81% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
8.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In OpenStack Nova before 33.0.2, the server create API does not strip certain hint data. The resulting instance has no Placement allocation.

CVSS v3
8.5
EG Score
8.5(medium)
EPSS
19.3%
KEV
Not listed

Published

June 16, 2026

Last Modified

June 26, 2026

Advisory Details (3)

Auto-updated Jun 16, 2026
No patch confirmed yet.
generic

oss-security - [OSSA-2026-022] OpenStack Nova: Nova scheduler hint injection bypasses Placement resource claims and scheduling constraints (CVE-2026-46448)

http://www.openwall.com/lists/oss-security/2026/06/16/5
generic

oss-security - [OSSA-2026-022] OpenStack Nova: Nova scheduler hint injection bypasses Placement resource claims and scheduling constraints (CVE-2026-46448)

https://www.openwall.com/lists/oss-security/2026/06/16/5
generic

Bug #2151252 “[OSSA-2026-022] Nova scheduler hint injection bypa...” : Bugs : OpenStack Compute (nova)

https://bugs.launchpad.net/nova/+bug/2151252

Vendor Advisories for CVE-2026-46448(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
nova33.0.0, 33.0.1——

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 34× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:24 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 02:29 UTCEPSS rescore
  6. 2026-07-18 10:04 UTCEPSS rescore
  7. 2026-07-16 17:03 UTCEPSS rescore
  8. 2026-07-15 16:57 UTCEPSS rescore
  9. 2026-07-15 02:00 UTCEPSS rescore
  10. 2026-07-13 22:30 UTCEPSS rescore
  11. 2026-07-13 06:13 UTCEPSS rescore
  12. 2026-07-12 05:46 UTCEPSS rescore
  13. 2026-07-11 08:27 UTCEPSS rescore
  14. 2026-07-09 19:10 UTCEPSS rescore
  15. 2026-07-08 15:16 UTCEPSS rescore
  16. 2026-07-07 13:46 UTCEPSS rescore
  17. 2026-07-06 16:27 UTCEPSS rescore
  18. 2026-07-06 02:23 UTCEPSS rescore
  19. 2026-07-05 02:30 UTCEPSS rescore
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-01 15:07 UTCEPSS rescore
  22. 2026-06-30 23:22 UTCEPSS rescore
  23. 2026-06-29 14:06 UTCEPSS rescore
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-28 14:07 UTCEPSS rescore
Show 22 more
  1. 2026-06-28 04:56 UTCEPSS rescore
  2. 2026-06-28 04:56 UTCEPSS rescore
  3. 2026-06-27 05:12 UTCEG score recompute▲ 3.10
  4. 2026-06-27 03:08 UTCEPSS rescore
  5. 2026-06-26 17:41 UTCNVD updateCVSS v3 → 8.5 · severity → HIGH
  6. 2026-06-25 13:49 UTCEPSS rescore
  7. 2026-06-24 14:05 UTCEPSS rescore
  8. 2026-06-23 21:33 UTCEPSS rescore
  9. 2026-06-23 21:33 UTCEPSS rescore
  10. 2026-06-22 14:25 UTCEPSS rescore
  11. 2026-06-22 14:25 UTCEPSS rescore
  12. 2026-06-21 14:56 UTCEPSS rescore
  13. 2026-06-21 14:56 UTCEPSS rescore
  14. 2026-06-21 01:59 UTCEPSS rescore
  15. 2026-06-21 01:59 UTCEPSS rescore
  16. 2026-06-19 19:26 UTCEPSS rescore
  17. 2026-06-19 19:26 UTCEPSS rescore
  18. 2026-06-18 17:52 UTCEPSS rescore
  19. 2026-06-18 17:52 UTCEPSS rescore
  20. 2026-06-17 17:53 UTCEPSS rescore
  21. 2026-06-16 21:07 UTCEG score recompute
  22. 2026-06-16 21:07 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-46448?
CVE-2026-46448 is a high vulnerability published on June 16, 2026. In OpenStack Nova before 33.0.2, the server create API does not strip certain hint data. The resulting instance has no Placement allocation.
When was CVE-2026-46448 disclosed?
CVE-2026-46448 was first published in the National Vulnerability Database on June 16, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46448 actively exploited?
CVE-2026-46448 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 19.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46448?
CVE-2026-46448 has a CVSS v3 base score of 8.5 (NVD).
How do I remediate CVE-2026-46448?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46448, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46448

Explore →

Is Your Infrastructure Affected by CVE-2026-46448?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs