Quick answers
- Is CVE-2026-45407 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45407 being exploited in the wild.
- How severe is CVE-2026-45407?
- Medium severity, with a CVSS score of 5, published 26 June 2026.
- Which products and versions are affected?
- Dokku < 0.38.2.
- Is there a fix for CVE-2026-45407?
- A patch was published on 2026-05-09: Pull request #8589 merged to enforce permissions. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-45407 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2026-45407?
- Check whether you run Dokku at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A vulnerability in Dokku's git:auth command stems from the use of the bash 'touch' command to initialize the $DOKKU_ROOT/.netrc file before the netrc binary can set its own restrictive permissions. Because 'touch' respects the system's default umask (typically 0644), the file is created with world-readable permissions, bypassing the netrc binary's intended 0600 (owner-only) setting. A local attacker with shell access to the Dokku host can read this file to obtain plaintext Git credentials. The issue is resolved in version 0.38.2, which explicitly enforces 0600 permissions and repairs existing installations.
Affected products
- Dokku Dokku < 0.38.2
Timeline
- 2026-05-09: patched: Pull request #8589 merged to enforce permissions.
- 2026-05-10: advisory: Release 0.38.2 published.
- 2026-06-26: disclosed: CVE-2026-45407 published.