CVE-2026-46447

HIGHNVD 7.75.8
EchelonGraph scoreMEDIUM confidence

Score 5.8 from GitHub Security Advisory published 2026-06-04. NVD baseline CVSS 7.7; sources differ by 1.9.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.7
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.7Exploit: NoneExposed: 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
5.8(medium)
EPSS
17.8%
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-07-16ubuntu

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.

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 8× in last 7d / 59× 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 112 total refreshes for this CVE.

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

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 17.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46447?
CVE-2026-46447 has a CVSS v3 base score of 7.7 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 5.8.
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

Explore the affected products and dependency analysis for 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.