Loading story…
Red Hat disclosed two Important GitPython vulnerabilities, CVE-2026-42215 and CVE-2026-42284, that can let attackers achieve arbitrary command execution when applications pass untrusted input into Git operations. CVE-2026-42215 stems from incomplete filtering of dangerous Git options supplied through crafted Python keyword arguments, affecting functions such as Repo.clone_from(), Remote.fetch(), Remote.pull(), and Remote.push(). CVE-2026-42284 affects the _clone() path and allows malicious use of the multi_options parameter to inject Git configuration like core.hooksPath, enabling execution of attacker-controlled hooks during clone operations.
The flaws map to CWE-88 argument injection, a weakness in which applications fail to properly neutralize argument delimiters and unintended options are interpreted by downstream commands. Red Hat assigned both issues a CVSS v3 score of 7.5, while external scoring for CVE-2026-42284 ranged higher, and said no acceptable mitigation is currently available under its product security criteria. Red Hat listed multiple products as affected, with some marked not affected or will not fix, and noted that GitPython 3.1.47 contains the upstream fix for CVE-2026-42215; the disclosures underscore the risk of passing user-controlled values into command or clone parameters without strict validation or argument separation.
See affected versions and whether adversaries are exploiting it.
6 events from the most recent confirmed update back to the earliest known activity.
Red Hat last modified its CVE-2026-42284 entry, including affected product status, severity scoring differences, and the statement that no acceptable mitigation is currently available under its product security criteria.
Red Hat last modified its CVE-2026-42215 entry, retaining details on affected and unaffected products, severity, and the lack of an acceptable mitigation under its product security criteria.
Red Hat published an advisory for CVE-2026-42284, describing an Important GitPython flaw in the _clone() function where malicious multi_options input can inject Git configuration such as core.hooksPath and trigger attacker-controlled hooks during clone operations.
Red Hat published an advisory for CVE-2026-42215, describing an Important GitPython vulnerability in which crafted keyword arguments can bypass safeguards in functions such as Repo.clone_from(), Remote.fetch(), Remote.pull(), and Remote.push() to enable arbitrary command execution.
MITRE's CWE Content Team updated the CWE-88 entry's applicable platforms and relationships as part of ongoing maintenance of the weakness definition.
MITRE's CWE Content Team updated the CWE-88 entry's observed examples, reflecting maintenance of the weakness record and its mapped real-world examples.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
3 references tracked. Mallory keeps watching after this page renders.
redhat.com
Open sourceredhat.com
Open sourcecwe.mitre.org
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Two high-severity vulnerabilities in **GitPython** allowed attackers to bypass built-in safety checks and reach arbitrary command execution through Git operations. **CVE-2026-42215** affects versions `3.1.30` through `3.1.46` and stems from GitPython validating blocked Git options before normalizing Python keyword arguments: values such as `upload_pack` could pass validation, then be converted into forbidden flags like `--upload-pack` when passed to `Repo.clone_from()`, `Remote.fetch()`, `Remote.pull()`, or `Remote.push()`. The flaw could let attacker-controlled input trigger command execution with the privileges of the Python process even when `allow_unsafe_options=False`. A second flaw, **CVE-2026-42284**, affects GitPython before version `3.1.47` and involves unsafe handling of the `multi_options` parameter in `_clone()`. The library checked `multi_options` before later reprocessing it with `shlex.split(" ".join(multi_options))`, enabling crafted input to smuggle additional Git command-line arguments past validation. A string that appeared to be a valid branch selection could be split into separate options, including malicious configuration such as `core.hooksPath`, causing Git to execute attacker-controlled hooks during clone. Both issues were fixed in **GitPython `3.1.47`**.
Jun 29, 2026
GitPython has disclosed seven vulnerabilities affecting multiple versions of the widely used Python library, exposing CI/CD and other automation environments to supply-chain risk. The most severe issue, **CVE-2026-73625** (`CVSS 8.8`), allows remote code execution by bypassing `check_unsafe_options` and smuggling unsafe Git options through crafted keyword arguments, enabling arbitrary command execution through parameters such as `--upload-pack`. Affected methods include `clone_from`, `fetch`, `pull`, `push`, `ls_remote`, `iter_commits`, `blame`, and `archive`, according to public advisories and CVE records. The broader disclosure also includes **CVE-2026-73622**, which can leak secrets by expanding environment variables in attacker-controlled URLs and writing them into `.git/config` or `.gitmodules`, as well as **CVE-2026-73620** and **CVE-2026-73624**, which permit arbitrary file read or overwrite through unsafe option forwarding in functions such as `IndexFile.checkout()`, `TagReference.create()`, and `Diffable.diff()`. GitHub advisories further describe related issues involving local file disclosure, git-directory creation outside the destination, unsafe configuration handling, and hook or template abuse. Fixes were released across versions **3.1.54**, **3.1.55**, **3.1.56**, and **3.1.57**, with reports indicating that upgrading to **GitPython 3.1.57** remediates all seven CVEs; no active exploitation was reported at publication time.
Aug 14, 2026
GitPython **3.1.50** contains a critical flaw tracked as `CVE-2026-67324` that lets attackers bypass the library’s default protection against unsafe clone options. The issue affects applications that pass attacker-influenced values into `Repo.clone_from`, particularly through `multi_options`, while relying on `allow_unsafe_options=False` to block dangerous arguments. The bypass works because GitPython fails to detect joined short-option forms such as `-u<value>`, allowing the blocked `--upload-pack`/`-u` option to slip through filtering. An attacker can supply `-u<helper>` during a clone operation and cause Git to execute an attacker-specified helper command, resulting in remote command execution consistent with **CWE-78**. The vulnerability is rated **critical** with CVSS `AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`, and the fix is available in **GitPython 3.1.51**.
Aug 2, 2026