CVE-2026-67322
GitPython clone URL expands env vars, leaking secrets to attacker-controlled hosts.
Is CVE-2026-67322 being exploited?
Not confirmed. CVE-2026-67322 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.27% probability of exploitation in the next 30 days.
How severe is CVE-2026-67322?
CVE-2026-67322 is rated High with a CVSS score of 8.7. 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-67322?
Yes. A fix has been recorded for CVE-2026-67322. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-67322 affect?
CVE-2026-67322 affects GitPython < 3.1.52, Applications using Repo.clone_from(), CI/CD systems and developer tools invoking GitPython. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-67322?
Upgrade GitPython to >=3.1.52, rotate exposed secrets, block untrusted clone URLs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker controlling clone URL can exfiltrate environment variables (e.g., AWS_SECRET_ACCESS_KEY, GITHUB_TOKEN) during Repo.clone_from().
Immediate action required
- affected< 3.1.52
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.