CVE-2026-73625
GitPython remote code execution via option-smuggling in check_unsafe_options
Is CVE-2026-73625 being exploited?
Not confirmed. CVE-2026-73625 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.65% probability of exploitation in the next 30 days.
How severe is CVE-2026-73625?
CVE-2026-73625 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-73625?
Yes. A fix has been recorded for CVE-2026-73625. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-73625 affect?
CVE-2026-73625 affects GitPython < 3.1.54, Python apps using GitPython, CI/CD systems, Dev workstations, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-73625?
Upgrade GitPython to >= 3.1.54 and audit CI/dev automation for unsafe option usage
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution: crafted option dicts to GitPython methods (e.g., clone_from, fetch, push, ls_remote) can execute OS commands via the --upload-pack parameter.
Patch when possible
- affected< 3.1.54
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.