CVE-2026-45405

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 79% 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
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

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

Dokku is a docker-powered PaaS. Prior to 0.38.2, the git:from-archive and certs:add commands extract user-supplied tar/zip archives into temporary directories without sanitizing member paths or preventing symlink traversal. GNU tar creates symlinks during extraction and follows them for subsequent entries, allowing an attacker to write arbitrary files anywhere writable by the dokku user — including overwriting ~/.ssh/authorized_keys to gain unrestricted shell access. This vulnerability is fixed in 0.38.2.

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
20.8%
KEV
Not listed

Published

June 26, 2026

Last Modified

June 26, 2026

Advisory Details (2)

Auto-updated Jun 26, 2026
Patch available. Sources: github_pr, github.
github Patch Available

Arbitrary File Write via Tar Symlink Traversal in git:from-archive and certs:add · Advisory · dokku/dokku · GitHub

https://github.com/dokku/dokku/security/advisories/GHSA-j6qq-xg73-ghqg
github_pr Patch Available

Harden archive extraction against symlink traversal

Patch available: dokku/dokku v0.38.2 (PR #8591 merged 2026-05-09)

https://github.com/dokku/dokku/pull/8591

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 50× 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-13 00:31 UTCEG score recompute
  2. 2026-07-12 12:04 UTCEG score recompute
  3. 2026-07-12 05:46 UTCEPSS rescore
  4. 2026-07-11 23:36 UTCEG score recompute
  5. 2026-07-11 11:09 UTCEG score recompute
  6. 2026-07-11 08:27 UTCEPSS rescore
  7. 2026-07-10 22:41 UTCEG score recompute
  8. 2026-07-10 10:12 UTCEG score recompute
  9. 2026-07-09 21:45 UTCEG score recompute
  10. 2026-07-09 19:10 UTCEPSS rescore
  11. 2026-07-09 09:16 UTCEG score recompute
  12. 2026-07-08 20:49 UTCEG score recompute
  13. 2026-07-08 15:16 UTCEPSS rescore
  14. 2026-07-08 08:22 UTCEG score recompute
  15. 2026-07-07 19:56 UTCEG score recompute
  16. 2026-07-07 13:46 UTCEPSS rescore
  17. 2026-07-07 07:28 UTCEG score recompute
  18. 2026-07-06 18:40 UTCEG score recompute
  19. 2026-07-06 16:27 UTCEPSS rescore
  20. 2026-07-06 06:11 UTCEG score recompute
  21. 2026-07-06 02:23 UTCEPSS rescore
  22. 2026-07-05 17:42 UTCEG score recompute
  23. 2026-07-05 05:15 UTCEG score recompute
  24. 2026-07-05 02:30 UTCEPSS rescore
  25. 2026-07-04 16:45 UTCEG score recompute
Show 25 more
  1. 2026-07-04 04:14 UTCEG score recompute
  2. 2026-07-03 15:45 UTCEG score recompute
  3. 2026-07-03 03:16 UTCEG score recompute
  4. 2026-07-02 14:49 UTCEG score recompute
  5. 2026-07-02 02:21 UTCEG score recompute
  6. 2026-07-01 15:07 UTCEPSS rescore
  7. 2026-07-01 13:54 UTCEG score recompute
  8. 2026-07-01 01:27 UTCEG score recompute
  9. 2026-06-30 23:22 UTCEPSS rescore
  10. 2026-06-30 12:59 UTCEG score recompute
  11. 2026-06-30 00:31 UTCEG score recompute
  12. 2026-06-29 14:06 UTCEPSS rescore
  13. 2026-06-29 14:06 UTCEPSS rescore
  14. 2026-06-29 12:04 UTCEG score recompute
  15. 2026-06-28 23:37 UTCEG score recompute
  16. 2026-06-28 14:07 UTCEPSS rescore
  17. 2026-06-28 11:09 UTCEG score recompute
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-28 04:56 UTCEPSS rescore
  20. 2026-06-27 22:42 UTCEG score recompute
  21. 2026-06-27 10:15 UTCEG score recompute
  22. 2026-06-26 21:47 UTCEG score recompute 0.20
  23. 2026-06-26 19:41 UTCNVD updateCVSS v3 → 8.8 · severity → HIGH
  24. 2026-06-26 17:41 UTCEG score recompute
  25. 2026-06-26 17:41 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-45405?
CVE-2026-45405 is a high vulnerability published on June 26, 2026. Dokku is a docker-powered PaaS. Prior to 0.38.2, the git:from-archive and certs:add commands extract user-supplied tar/zip archives into temporary directories without sanitizing member paths or preventing symlink traversal. GNU tar creates symlinks during extraction and follows them for subsequent…
When was CVE-2026-45405 disclosed?
CVE-2026-45405 was first published in the National Vulnerability Database 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-45405 actively exploited?
CVE-2026-45405 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 20.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-45405?
CVE-2026-45405 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-45405?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45405, 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-45405

Explore →

Is Your Infrastructure Affected by CVE-2026-45405?

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