CVE-2026-124039: Gitleaks through 8.30.1 contains an incorrect permission assignment vulnerability that allows local users to r

Q: How do I fix CVE-2026-124039?

gitleaks: upgrade to newer than 8.30.1. Exact commands for each OS are on this page.

Q: Is CVE-2026-124039 being exploited?

CVE-2026-124039 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-124039 affect?

CVE-2026-124039 affects gitleaks. Severity is low (CVSS 3.3). 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 pas

Q: How urgent is CVE-2026-124039?

Priority 12/100. No elevated risk signals yet.

Routine

LOW 3.3UPGRADE

CVE-2026-124039 is a low-severity flaw (CVSS 3.3) affecting gitleaks. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	3.3 (Low)
EPSS exploit chance	n/a
CISA exploited list	No
Weakness	CWE-732
Published	2026-11-06
Last modified	2026-11-06

Publisher (CNA): VulnCheck · Vendor: gitleaks · Source: CVE Program record (NVD analysis pending)

Last updated 2026-11-06 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-11-06 19:14 UTCPublished CVE record published
2026-11-06 19:14 UTCUpdated Record last modified

gitleaks gitleaks UPGRADE

Affected: <= 8.30.1

Fixed in: newer than 8.30.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy gitleaks || rpm -q gitleaks || gitleaks --version

2. UPGRADE to newer than 8.30.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade gitleaks

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade gitleaks

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-124039?

gitleaks: upgrade to newer than 8.30.1. Exact commands for each OS are on this page.

Is CVE-2026-124039 being exploited?

CVE-2026-124039 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-124039 affect?

CVE-2026-124039 affects gitleaks. Severity is low (CVSS 3.3). 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 pas

How urgent is CVE-2026-124039?

Priority 12/100. No elevated risk signals yet.

References

← Back to latest CVEs