Dokku is a docker-powered PaaS. Prior to 0.38.2, the git:auth command creates $DOKKU_ROOT/.netrc using bash's touch command, which applies the default umask of 0644. This pre-creation defeats the netrc binary's built-in 0600 permission setting, leaving git credentials readable by any local user who can traverse the dokku home directory. This vulnerability is fixed in 0.38.2.
CVE-2026-45407
This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 99% 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).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.5
- EG Score
- 5.5(medium)
- EG Risk
- 29(Track)EG Risk 29/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 computedSeverity55% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 0.5%
- KEV
- Not listed
Published
June 26, 2026
Last Modified
June 26, 2026
Advisory Details (2)
Auto-updated Jun 26, 2026Git Credentials in .netrc Stored World-Readable Due to Premature touch · Advisory · dokku/dokku · GitHub
https://github.com/dokku/dokku/security/advisories/GHSA-xh7p-9crg-pchrEnforce 0600 permissions on .netrc credentials file
Patch available: dokku/dokku v0.38.2 (PR #8589 merged 2026-05-09)
https://github.com/dokku/dokku/pull/8589Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 26× 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.
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:16 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 19:24 UTCEG score recompute▲ 0.50
- 2026-06-26 19:41 UTCNVD updateCVSS v3 → 5.5
- 2026-06-26 17:41 UTCEG score recompute
Show 1 moreShow fewer
- 2026-06-26 17:41 UTCNVD updatefirst tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-522
- CVE-2013-7055EG 9.8EPSS 93%CRITICAL
- CVE-2013-7052EG 9.8EPSS 98%CRITICAL
- CVE-2014-3445EG 9.8EPSS 92%CRITICAL
- CVE-2014-5381EG 9.8EPSS 94%CRITICAL
- CVE-2014-5093EG 9.8CRITICAL
- CVE-2016-4401EG 9.8CRITICAL
- CVE-2018-1000627EG 9.8CRITICAL
- CVE-2018-11742EG 9.8EPSS 96%CRITICAL
- CVE-2018-1000851EG 9.8CRITICAL
- CVE-2018-10824EG 9.8EPSS 96%CRITICAL
Frequently asked(5)
What is CVE-2026-45407?
When was CVE-2026-45407 disclosed?
Is CVE-2026-45407 actively exploited?
What is the CVSS score of CVE-2026-45407?
How do I remediate CVE-2026-45407?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-45407
Is Your Infrastructure Affected by CVE-2026-45407?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.