CVE-2026-46447

HIGHNVD 7.77.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.7 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 82% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.7Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.7
EG Score
7.7(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity77% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
18%
KEV
Not listed

Published

June 3, 2026

Last Modified

July 22, 2026

Advisory Details (3)

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

oss-security - [OSSA-2026-017] Ironic: Script injection during node boot via linux command line override (CVE-2026-46447)

http://www.openwall.com/lists/oss-security/2026/06/03/11
generic

OSSA-2026-017: Script injection during node boot via linux command line override — OpenStack Security Advisories 0.0.1.dev342 documentation

https://security.openstack.org/ossa/OSSA-2026-017.html
generic

Bug #2150624 “[OSSA-2026-017] Boot Script Injection via Unsaniti...” : Bugs : Ironic

https://bugs.launchpad.net/ironic/+bug/2150624

Vendor Advisories for CVE-2026-46447(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3-ironic (1:20.1.0-0ubuntu1.3) @ jammy2026-09-14ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
ironic1:16.0.3-1 ... 1:35.0.1-8 (66 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
ironic1:21.1.0-3 ... 1:21.4.0-4 (7 versions)1:21.4.4-0+deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
ironic1:29.0.0-7, 1:29.0.5-0+deb13u11:29.0.5-0+deb13u2—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
ironic1:29.0.0-7 ... 1:35.0.1-3 (13 versions)1:35.0.1-5—
PyPI(1)
PackageVulnerable rangeFixed inDependents
ironic17.0.0 ... 35.0.1 (71 versions)35.0.2—

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 9× in last 7d / 38× 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.

Showing the most recent 100 of 233 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-17 19:31 UTCEPSS rescore
  3. 2026-09-16 14:08 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-14 05:39 UTCEG score recompute
  6. 2026-09-14 05:39 UTCVendor advisory
  7. 2026-09-13 16:47 UTCEPSS rescore
  8. 2026-09-12 23:36 UTCOSV refresh
  9. 2026-09-12 15:01 UTCEPSS rescore
  10. 2026-09-11 14:53 UTCEPSS rescore
  11. 2026-09-11 09:37 UTCEPSS rescore
  12. 2026-09-10 09:34 UTCEPSS rescore
  13. 2026-09-08 22:00 UTCEPSS rescore
  14. 2026-09-07 16:01 UTCEPSS rescore
  15. 2026-09-06 13:47 UTCEPSS rescore
  16. 2026-09-04 05:06 UTCEPSS rescore
  17. 2026-09-02 14:12 UTCEPSS rescore
  18. 2026-09-01 13:54 UTCEPSS rescore
  19. 2026-08-30 19:17 UTCEPSS rescore
  20. 2026-08-30 01:22 UTCEPSS rescore
  21. 2026-08-28 21:41 UTCEPSS rescore
  22. 2026-08-27 14:25 UTCEPSS rescore
  23. 2026-08-26 14:46 UTCEPSS rescore
  24. 2026-08-25 13:49 UTCEPSS rescore
  25. 2026-08-25 03:42 UTCEG score recompute
Show 75 more
  1. 2026-08-25 03:42 UTCVendor advisory
  2. 2026-08-24 00:45 UTCVendor advisory
  3. 2026-08-23 13:37 UTCEG score recompute
  4. 2026-08-23 13:37 UTCVendor advisory
  5. 2026-08-23 00:19 UTCEPSS rescore
  6. 2026-08-21 23:49 UTCEPSS rescore
  7. 2026-08-21 20:13 UTCVendor advisory
  8. 2026-08-21 08:36 UTCEG score recompute
  9. 2026-08-21 08:36 UTCVendor advisory
  10. 2026-08-20 22:55 UTCEPSS rescore
  11. 2026-08-20 21:20 UTCVendor advisory
  12. 2026-08-20 10:07 UTCEG score recompute
  13. 2026-08-20 10:07 UTCVendor advisory
  14. 2026-08-19 17:04 UTCEPSS rescore
  15. 2026-08-18 13:48 UTCEPSS rescore
  16. 2026-08-17 15:59 UTCEG score recompute
  17. 2026-08-17 15:59 UTCVendor advisory
  18. 2026-08-17 13:47 UTCEPSS rescore
  19. 2026-08-17 04:01 UTCVendor advisory
  20. 2026-08-16 14:57 UTCEG score recompute
  21. 2026-08-16 14:57 UTCVendor advisory
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 02:18 UTCEG score recompute
  24. 2026-08-16 02:18 UTCVendor advisory
  25. 2026-08-16 02:14 UTCEPSS rescore
  26. 2026-08-15 14:55 UTCEG score recompute
  27. 2026-08-15 14:55 UTCVendor advisory
  28. 2026-08-15 01:30 UTCEPSS rescore
  29. 2026-08-14 21:29 UTCVendor advisory
  30. 2026-08-14 10:21 UTCVendor advisory
  31. 2026-08-13 23:14 UTCEG score recompute
  32. 2026-08-13 23:14 UTCVendor advisory
  33. 2026-08-13 22:00 UTCEPSS rescore
  34. 2026-08-13 07:58 UTCVendor advisory
  35. 2026-08-12 19:47 UTCEG score recompute
  36. 2026-08-12 19:47 UTCVendor advisory
  37. 2026-08-12 13:51 UTCEPSS rescore
  38. 2026-08-12 08:38 UTCVendor advisory
  39. 2026-08-11 21:29 UTCEG score recompute
  40. 2026-08-11 21:29 UTCVendor advisory
  41. 2026-08-11 10:21 UTCEG score recompute
  42. 2026-08-11 10:21 UTCVendor advisory
  43. 2026-08-11 00:00 UTCEPSS rescore
  44. 2026-08-10 23:14 UTCVendor advisory
  45. 2026-08-10 12:07 UTCVendor advisory
  46. 2026-08-10 00:56 UTCVendor advisory
  47. 2026-08-09 13:48 UTCEG score recompute
  48. 2026-08-09 13:48 UTCVendor advisory
  49. 2026-08-09 13:46 UTCEPSS rescore
  50. 2026-08-09 02:40 UTCEG score recompute
  51. 2026-08-09 02:40 UTCVendor advisory
  52. 2026-08-08 16:37 UTCEPSS rescore
  53. 2026-08-08 15:32 UTCVendor advisory
  54. 2026-08-08 04:13 UTCVendor advisory
  55. 2026-08-07 17:06 UTCEG score recompute
  56. 2026-08-07 17:06 UTCVendor advisory
  57. 2026-08-07 05:58 UTCVendor advisory
  58. 2026-08-06 18:50 UTCEG score recompute
  59. 2026-08-06 18:50 UTCVendor advisory
  60. 2026-08-06 13:47 UTCEPSS rescore
  61. 2026-08-06 07:43 UTCVendor advisory
  62. 2026-08-05 20:34 UTCEG score recompute
  63. 2026-08-05 20:34 UTCVendor advisory
  64. 2026-08-05 19:17 UTCEPSS rescore
  65. 2026-08-04 19:34 UTCEG score recompute
  66. 2026-08-04 19:34 UTCVendor advisory
  67. 2026-08-04 15:10 UTCEPSS rescore
  68. 2026-08-04 10:39 UTCEPSS rescore
  69. 2026-08-04 02:57 UTCVendor advisory
  70. 2026-08-03 15:44 UTCEG score recompute
  71. 2026-08-03 15:44 UTCVendor advisory
  72. 2026-08-03 10:36 UTCEPSS rescore
  73. 2026-08-02 22:54 UTCVendor advisory
  74. 2026-08-02 11:47 UTCEG score recompute
  75. 2026-08-02 11:47 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-46447?
CVE-2026-46447 is a high vulnerability published on June 3, 2026. OpenStack Ironic before 35.0.2 allows Boot Script Injection of an iPXE script if the attacker can set node.driverinfo or node.instanceinfo.
When was CVE-2026-46447 disclosed?
CVE-2026-46447 was first published in the National Vulnerability Database on June 3, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46447 actively exploited?
CVE-2026-46447 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 81.7% of all scored CVEs.
What is the CVSS score of CVE-2026-46447?
CVE-2026-46447 has a CVSS v3 base score of 7.7 (NVD).
How do I remediate CVE-2026-46447?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46447, 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-46447

Explore →

Is Your Infrastructure Affected by CVE-2026-46447?

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

Start Free Scan →Browse All CVEs