VulnerabilityPublished 13 Aug 2026Updated 26 Oct 2026

CVE-2026-67322: GitPython · Environment-variable exfiltration via os.path.expandvars() on Repo.clone_from() URL

Affects snakemakeSource GCVE Database

Authoritative record:CVE-2026-67322· High 8.7

Not known to be exploited · CVSS 8.7 High : upgrade to 9.23.1_1 soon.

Data as of 26 Oct 2026, 19:31 UTC

CVSS 4.0 base score

8.7High

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 9.23.1_1

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 1 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade snakemake to 9.23.1_1.

Affected software

Product	Affected	Fixed in
Homebrewsnakemake`pkg:brew/snakemake`Other threats	Affected >=5.5.3 <9.23.1_1	Fixed in 9.23.1_1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in GitPython version 9.23.1_1 that removes the unsafe environment variable expansion from clone URLs. Users should upgrade to this version or later to remediate the vulnerability. Until patched, avoid passing untrusted URLs to Repo.clone_from() or ensure environment variables do not contain sensitive data accessible to the GitPython process. No other mitigations are documented.

Description

GitPython versions up to 3.1.50 contain a vulnerability where the Repo.clone_from() method passes the remote URL through os.path.expandvars(), causing environment variables in the URL to be expanded. This can lead to secret environment variables being embedded in the URL and exfiltrated to an attacker-controlled host. The flaw arises because polish_url() applies environment variable expansion indiscriminately to remote URLs without validation or opt-out. A fix is available in version 9.23.1_1.

Impact

An attacker able to supply a clone URL to Repo.clone_from() can exfiltrate sensitive environment variables from the server process by embedding environment variable tokens in the URL. This leads to disclosure of secrets such as AWS keys or GitHub tokens without authentication or additional preconditions beyond URL submission. The vulnerability can also facilitate bypass of unsafe protocol checks if environment variables are attacker-controlled. The impact is high confidentiality loss with no integrity or availability impact.

Summary

The vulnerability in GitPython (CVE-2026-67322) occurs because the Repo.clone_from() method calls Git.polish_url() on the remote URL, which on non-Cygwin platforms uses os.path.expandvars() to expand environment variables in the URL string. An attacker controlling the URL can embed tokens like ${AWS_SECRET_ACCESS_KEY}, which are expanded server-side to reveal secret environment variables. The expanded URL containing secrets is then passed to git clone, which sends network requests to the attacker-controlled host, leaking sensitive data. The unsafe-protocol check is performed on the raw URL before expansion, allowing potential bypasses if environment variables are also attacker-controlled. This issue affects all GitPython releases up to and including 3.1.50 and is fixed in version 9.23.1_1.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Oct 2026, 19:31 UTC

Technical details

References

Community reviews

Related threats