Skip to content
Applications

CVE-2026-63728

8.1
High
EPSS 0.21%Patch availableJul 21, 2026

Template injection in Gitleaks allows env var disclosure and secret exfiltration via DNS.

common questions

Is CVE-2026-63728 being exploited?

Not confirmed. CVE-2026-63728 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.21% probability of exploitation in the next 30 days.

How severe is CVE-2026-63728?

CVE-2026-63728 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-63728?

Yes. A fix has been recorded for CVE-2026-63728. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-63728 affect?

CVE-2026-63728 affects Gitleaks < 8.30.1, CI/CD runners using Gitleaks, Developer workstations running Gitleaks. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-63728?

Upgrade to Gitleaks 8.30.1+ and restrict/validate report templates; limit runner env secrets.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Gitleaks < 8.30.1CI/CD runners using GitleaksDeveloper workstations running Gitleaks
impact

Attackers controlling report templates can read arbitrary env vars and exfiltrate credentials, tokens, and API keys via DNS queries.

action required

Patch when possible

affected versions
gitleaks gitleaks
  • affected< 8.30.1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free