VulnerabilityPublished 29 Oct 2026

CVE-2026-110855: GitPython · separate_git_dir leaks env vars via crafted .gitmodules submodule name

Affects kimi-cliSource GCVE Database

Compare

Authoritative record:CVE-2026-110855· High 7.1

Not known to be exploited · CVSS 7.1 High : upgrade to 1.50.0 soon.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score

7.1High

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/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: Passive
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: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
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 14 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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 kimi-cli to 1.50.0.

Affected software

Product	Affected	Fixed in
Homebrewkimi-cli`pkg:brew/kimi-cli`Other threats	Affected >=1.11.0 <1.50.0	Fixed in 1.50.0

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

AI-suggested

Upgrade GitPython to version 1.50.0 or later, where this vulnerability is fixed. The fix disables environment variable expansion for the separate_git_dir parameter derived from untrusted submodule names. If upgrading is not immediately possible, avoid cloning repositories with untrusted submodules or disable DEBUG-level logging to reduce exposure of leaked environment variables in logs. No other mitigations are documented.

Description

GitPython versions >=1.11.0 and <1.50.0 contain a vulnerability in the handling of the separate_git_dir parameter during cloning. The flaw allows environment variable expansion from attacker-controlled .gitmodules submodule names, leading to leakage of environment variable values on disk and in debug logs. This occurs because the polish_url function expands environment variables without disabling this behavior for untrusted input. The vulnerability is fixed in version 1.50.0.

Impact

An attacker controlling a Git repository can craft submodule names that cause environment variables in the victim's environment to be expanded and leaked. This leads to disclosure of sensitive environment variable values persistently on disk (in directory names) and temporarily in debug logs if DEBUG-level logging is enabled. The impact is confidentiality loss of environment variables, which may include secrets or credentials. There is no indication of code execution or integrity impact. The CVSS 3.1 score is 6.5 (medium severity) reflecting network attack vector, low attack complexity, no privileges required, user interaction required, and high confidentiality impact.

Summary

The vulnerability in GitPython arises from the _clone() method's handling of the separate_git_dir argument, which is derived from the .gitmodules submodule name—a fully attacker-controlled value. Unlike other calls to Git.polish_url(), this call does not disable environment variable expansion, allowing an attacker to craft submodule names containing environment variable syntax (e.g., $VAR). When cloning and updating submodules, the environment variable is expanded, leaking its value in the directory name created under .git/modules/ and in debug-level logging output of subprocess calls. The flaw was not addressed in prior related fixes that added expand_vars=False to other polish_url calls. The vulnerability affects GitPython versions from 1.11.0 up to but not including 1.50.0, with a fix available in 1.50.0.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Oct 2026, 06:44 UTC

Technical details

References

Community reviews

Related threats