VulnerabilityPublished 29 Oct 2026

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

Affects jiratuiSource GCVE Database

Compare

Authoritative record:CVE-2026-110855· High 7.1

Not known to be exploited · CVSS 7.1 High.

Data as of 30 Oct 2026, 08:46 UTC

CVSS 4.0 base score

7.1High

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

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

Affected software

Product	Affected	Fixed in
Homebrewjiratui`pkg:brew/jiratui`Other threats	Affected >=1.3.0	Fixed in–

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

AI-suggested

As of the provided data, no explicit patch or fix release is mentioned. Until a fix is available, avoid cloning and updating submodules from untrusted repositories, especially in environments where DEBUG-level logging is enabled. Consider disabling or restricting DEBUG logging for GitPython operations to prevent secret leakage in logs. Monitor vendor advisories for updates and apply official fixes once released.

Description

GitPython's Repo._clone() method improperly expands environment variables in the separate_git_dir parameter derived from attacker-controlled .gitmodules submodule names. This leads to leakage of environment variable values as directory names on disk and in debug logs when cloning and updating submodules from a malicious repository. The vulnerability arises because Git.polish_url() is called without disabling variable expansion on untrusted input, contrary to other similar call sites. This can expose sensitive environment variables persistently on disk and in verbose logs.

Impact

An attacker controlling a malicious Git repository can cause environment variables from the victim's environment to be expanded and leaked as directory names on disk and in debug-level logs during normal clone and submodule update operations. This can disclose sensitive environment variables such as secret keys or tokens persistently on the victim's filesystem and in logs that may be accessible to other users or processes. There is no direct integrity or availability impact. Exploitation requires the victim to clone and update submodules from a malicious repository with DEBUG logging enabled to observe logs containing the secret. The vulnerability does not require elevated privileges but does require user interaction (cloning the malicious repo).

Summary

The vulnerability in GitPython (CVE-2026-110855) stems from the _clone() method's handling of the separate_git_dir argument, which is derived from the .gitmodules submodule name — attacker-controlled data. Unlike other uses of 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 a repository is cloned and submodules updated, the environment variable expands to its value, which is then used as a directory name under .git/modules/ and appears in debug-level Popen subprocess logs unredacted. This disclosure channel persists on disk and leaks secrets if DEBUG logging is enabled. The flaw was confirmed by reproducing with a malicious repository and a victim environment variable, demonstrating the expanded secret appearing as a directory name and in logs. The vulnerability affects GitPython versions >=1.3.0. The CVSS 3.1 score is 6.5 (medium severity) with network attack vector, low attack complexity, no privileges required, user interaction required, and high confidentiality impact but no integrity or availability impact.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Oct 2026, 08:46 UTC

Technical details

References

Community reviews

Related threats