CVE-2026-114145: Jiratui · GitPython validates a submodule's ".git" path only after cloning into it (RCE)
Affects jiratuiSource GCVE Database
Not known to be exploited · CVSS 7.5 High.
Data as of 30 Oct 2026, 08:45 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 7.5 |
|---|
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 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.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewjiratuipkg:brew/jiratuiOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The vulnerability exists because validation occurs after the clone operation, allowing the malicious hook to be planted before rejection. Users should avoid passing untrusted or attacker-influenced paths to create_submodule. If using versions 3.2.0 or later, be aware that although a ValueError is raised for invalid paths, the malicious hook may still be present and executable. Until an official fix is released, manual inspection and cleaning of the .git/hooks directory after submodule creation is recommended. Monitor vendor advisories for updates and patches addressing the validation order.
Description
Jiratui's GitPython integration has a vulnerability where the create_submodule function clones a submodule into the .git/hooks directory before validating the path, allowing an attacker to plant a malicious executable hook. This hook executes on subsequent git operations, enabling arbitrary code execution. Versions from 3.1.x through 3.2.0+ are affected, with 3.1.x silently planting the hook and 3.2.0+ raising a ValueError only after the malicious hook is already written. The vulnerability requires an attacker-controlled submodule path and an empty or minimal .git/hooks directory.
References
- github.com/gitpython-developers/GitPython/security/advisories/GHSA-83vg-56qc-22m7 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-114145 (opens in a new tab)
- github.com/gitpython-developers/GitPython/pull/2264 (opens in a new tab)
- github.com/gitpython-developers/GitPython/commit/97eadb888d2f99567e3113f4e455be4ca128f697 (opens in a new tab)
- github.com/gitpython-developers/GitPython (opens in a new tab)
- github.com/gitpython-developers/GitPython/releases/tag/3.2.1 (opens in a new tab)