CVE-2026-42215 | GitPython: Command injection via Git options bypass

Exp

GitPython is a python library used to interact with Git repositories. From version 3.1.30 to before version 3.1.47, GitPython blocks dangerous Git options such as --upload-pack and --receive-pack by default, but the equivalent Python kwargs upload_pack and receive_pack bypass that check. If an application passes attacker-controlled kwargs into Repo.clone_from(), Remote.fetch(), Remote.pull(), or Remote.push(), this leads to arbitrary command execution even when allow_unsafe_options is left at its default value of False. This issue has been patched in version 3.1.47.

Published: 2026-05-07 Last update: 2026-05-11 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-42215 is rated Exploit Available (53.3/100): CVSS High severity, with low exploitation likelihood (EPSS 0.03%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2026-42215

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2026-42215

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-22 0.09% 0.03% -0.06%
2 2026-05-08 — 0.09% —

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-42215

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 [email protected]

Weakness enumeration for CVE-2026-42215

GitHub Security Advisory for CVE-2026-42215

GHSA-rpm5-65cw-6hj4 · Severity: high · Ecosystem: pip — GitPython has Command Injection via Git options bypass

OS Trackers for CVE-2026-42215

vendor priority summary link
debian not yet assigned CVE-2026-42215 not yet assigned priority: Debian including 1 source packages (python-git), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 3, resolved 2. https://security-tracker.debian.org/tracker/CVE-2026-42215
suse high — https://www.suse.com/security/cve/CVE-2026-42215/
ubuntu medium CVE-2026-42215 medium priority: Ubuntu including 1 source packages (python-git), 9 status rows across 9 suites (bionic, focal, jammy, noble, questing, resolute, trusty, upstream, xenial): released 7, ignored 1, needed 1. https://ubuntu.com/security/CVE-2026-42215

Affected software / configurations for CVE-2026-42215

Vendor Product Version Raw CPE
gitpython_project gitpython >= 3.1.30, < 3.1.47 cpe:2.3:a:gitpython_project:gitpython:*:*:*:*:*:python:*:*

References for CVE-2026-42215

cvelogic Threat Intelligence