CVE-2026-46447
No exploitation reported by the sources we read.
- Published2026-06-03
- Fixed in35.0.2 · 32.0.2 · 29.0.6 · 26.1.7
- WeaknessCWE-669
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
OpenStack Ironic before 35.0.2 allows Boot Script Injection of an iPXE script if the attacker can set node.driver_info or node.instance_info.
Timeline
dates in UTC- 2026-06-0322:16CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-46447?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-46447?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD · OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 35.0 | ≥ 33.0.0, < 35.0.2 | 35.0.2 | NVD · OSV |
| 32.0 | ≥ 30.0.0, < 32.0.2 | 32.0.2 | NVD · OSV |
| 29.0 | ≥ 27.0.0, < 29.0.6 | 29.0.6 | NVD · OSV |
| 26.1 | ≥ 17.0.0, < 26.1.7 | 26.1.7 | NVD · OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Openstack ironic to 35.0.2 · 32.0.2 · 29.0.6 · 26.1.7
Advisories and patches
- security.openstack.orgPatch · Vendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N
- Published
- 2026-06-03
- Last Modified
- 2026-07-22
- NVD status
- Modified
Frequently asked questions
What is CVE-2026-46447?
Is CVE-2026-46447 actively exploited?
What is the CVSS score for CVE-2026-46447?
Running ironic? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.