CVE-2026-48681

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 54% 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 — 3 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.1Exploit: None knownExposed: 0

A fix is available — apply it.

OpenStack Ironic through before 35.0.2 allows file overwrite via directory traversal during deployment with a crafted ISO image.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity81% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
46%
KEV
Not listed

Published

June 4, 2026

Last Modified

July 22, 2026

Advisory Details (3)

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

oss-security - [OSSA-2026-018] Ironic: File overwrite on Ironic conductor via path traversal in ISO handling (CVE-2026-48681)

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

oss-security - [OSSA-2026-018] Ironic: File overwrite on Ironic conductor via path traversal in ISO handling (CVE-2026-48681)

https://www.openwall.com/lists/oss-security/2026/06/03/12
generic

Bug #2148333 “[OSSA-2026-018] Path traversal during ISO extracti...” : Bugs : Ironic

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

Vendor Advisories for CVE-2026-48681(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:32.0.0-0ubuntu1.1) @ questing2026-08-25ubuntu

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 15× in last 7d / 84× 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 210 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-48681?
CVE-2026-48681 is a high vulnerability published on June 4, 2026. OpenStack Ironic through before 35.0.2 allows file overwrite via directory traversal during deployment with a crafted ISO image.
When was CVE-2026-48681 disclosed?
CVE-2026-48681 was first published in the National Vulnerability Database on June 4, 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-48681 actively exploited?
CVE-2026-48681 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 53.8% of all scored CVEs.
What is the CVSS score of CVE-2026-48681?
CVE-2026-48681 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-48681?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48681, 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-48681

Explore →

Is Your Infrastructure Affected by CVE-2026-48681?

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

Start Free Scan →Browse All CVEs