Loading vulnerability…
CVE-2026-42215 is an arbitrary command-execution vulnerability in GitPython versions 3.1.30 through 3.1.46. GitPython checks its unsafe Git-option blocklist before converting Python keyword argument names to Git command-line options. Consequently, underscore-form kwargs such as upload_pack and receive_pack bypass checks intended to reject the corresponding dangerous Git options. The affected interfaces are Repo.clone_from(), Remote.fetch(), Remote.pull(), and Remote.push(). The issue is exploitable with allow_unsafe_options set to its default value of False.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
15 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An arbitrary command execution vulnerability in GitPython caused by bypassing dangerous Git option checks via specially crafted keyword arguments to repository interaction functions.
A command-injection vulnerability in GitPython's unsafe Git-option blocklist. Git long-option prefix abbreviations can bypass the blocklist and cause execution of arbitrary commands.
A previously referenced GitPython vulnerability/fix concerning unsafe Git option handling in fetch, pull, push, and clone_from. It is mentioned only as background comparison to CVE-2026-67323.
The earlier GitPython command-injection issue for which version 3.1.47 introduced an unsafe Git-option blocklist. That exact-match blocklist was incomplete because it did not handle Git long-option prefix abbreviations.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.