Gitleaks prior to 8.30.1 contains a template injection vulnerability that allows attackers who can supply or influence report templates to read arbitrary environment variables and exfiltrate sensitive data by leveraging non-hermetic Sprig template functions. Attackers can craft malicious report templates using the env, expandenv, and getHostByName functions to extract credentials, tokens, and API keys from the host process and exfiltrate them through DNS queries, including secrets discovered during the scan itself.
CVE-2026-63728
Score 6.3 from GitHub Security Advisory (severity: HIGH) published 2026-07-21. a secondary CVSS source baseline 6.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.3
- EG Score
- 6.3(high)
- EG Risk
- 44(Track)EG Risk 44/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity63% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 4.2%
- KEV
- Not listed
Published
July 20, 2026
Last Modified
July 22, 2026
Advisory Details (4)
Auto-updated Jul 22, 2026Gitleaks: Abusing Sprig Template Functions for Secret Exfiltration | Fatih's Blog
https://fatihhcelik.github.io/posts/gitleaks-abusing-sprig-for-exfiltration/#the-fixGitleaks Secret Exfiltration via Non-Hermetic Sprig Template Functions in Report Template Feature | Advisories | VulnCheck
https://www.vulncheck.com/advisories/gitleaks-secret-exfiltration-via-non-hermetic-sprig-template-functions-in-report-template-featurecommit 83d9cd684c87 (gitleaks/gitleaks)
Fix landed in gitleaks/gitleaks commit 83d9cd684c87 — awaiting tagged release
https://github.com/gitleaks/gitleaks/commit/83d9cd684c87d95d656c1458ef04895a7f1cbd8eGitHub - gitleaks/gitleaks: Find secrets with Gitleaks 🔑 · GitHub
https://github.com/gitleaks/gitleaksVendor Advisories for CVE-2026-63728(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 11× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 03:22 UTCEG score recompute
- 2026-07-22 23:26 UTCEG score recompute
- 2026-07-22 23:26 UTCGHSA enrichment
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-21 01:49 UTCEG score recompute
- 2026-07-21 01:49 UTCGHSA enrichment
- 2026-07-20 23:48 UTCEG score recompute
- 2026-07-20 23:47 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-63728?
When was CVE-2026-63728 disclosed?
Is CVE-2026-63728 actively exploited?
What is the CVSS score of CVE-2026-63728?
How do I remediate CVE-2026-63728?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-63728
Is Your Infrastructure Affected by CVE-2026-63728?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.