CVE-2026-124039 Gitleaks through 8.30.1 World-Readable Report Files via --report-path
Medium 4.8
Published
Updated
Check this codebase for CVE-2026-124039 and fix it if it is affected.
What it is: CVE-2026-124039 is a medium-severity vulnerability in gitleaks, published on 6 Nov 2026.
Exploitation: There is no known exploitation of CVE-2026-124039 in the wild and no public exploit code.
Affected product: gitleaks. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-124039/ (Markdown: https://insights.sbomify.com/CVE-2026-124039/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-124039?
CVE-2026-124039 is a medium-severity vulnerability in gitleaks, published on 6 Nov 2026.
Official description
Gitleaks through 8.30.1 contains an incorrect permission assignment vulnerability that allows local users to read scan reports because cmd/root.go creates the --report-path file with os.Create and default permissions. Unless --redact is passed, other local users on shared hosts or CI runners can read plaintext secrets and matching lines to obtain discovered credentials.
Weakness: CWE-732
Which versions are affected by CVE-2026-124039?
How do I fix CVE-2026-124039?
No fix has been published for CVE-2026-124039 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-124039 being exploited?
There is no known exploitation of CVE-2026-124039 in the wild and no public exploit code.
Sources
Also known as GHSA-w4h6-9gpx-7gm5.