Vulnerability in Dokku (CVE-2026-45407)
Summary
Vulnerability in Dokku (CVE-2026-45407). Confidential information can be exposed externally. Mitigation: upgrade to 0.38.2 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-45407 has been found in Dokku.
Confidential information can be exposed externally. CVSS score: 5.0/10.
What to do: upgrade Dokku to 0.38.2 or later.
If unsure, ask your IT team or search "Dokku CVE-2026-45407" on the vendor's site.
CVE-2026-45407 (Dokku) — CWE-522 / CVSS v3 5.0
Attack vector: local
Patched: 0.38.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-522) exists in Dokku.
Check the vendor advisory for the affected versions of Dokku.
Severity: Medium (CVSS 5.0/10). Confidential information can be exposed externally.
Update to 0.38.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Dokku' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Dokku' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Dokkuを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Dokku to 0.38.2ステージング環境で 0.38.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。