CVE-2026-42215
OS command injection via attacker-controlled kwargs in GitPython methods.
Is CVE-2026-42215 being exploited?
Not confirmed. CVE-2026-42215 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.75% probability of exploitation in the next 30 days.
How severe is CVE-2026-42215?
CVE-2026-42215 is rated High with a CVSS score of 8.8. 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-42215?
Yes. A fix has been recorded for CVE-2026-42215. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-42215 affect?
CVE-2026-42215 affects GitPython (<3.1.47), Python apps using GitPython. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-42215?
Upgrade to 3.1.47 or newer
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution via crafted kwargs in Repo.clone_from(), fetch(), pull(), or push; bypasses default unsafe-option checks.
Patch when possible
- affected>= 3.1.30 and < 3.1.47
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.