CVE-2026-11968: TortoiseGit · Argument Injection
Affects TortoiseGitSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium : upgrade to 2.19.0 when convenient.
Data as of 5 Nov 2026, 00:01 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.19.0
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 24 Jun 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 5 Nov 2026.
What to do
Upgrade TortoiseGit to 2.19.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| TortoiseGit teamTortoiseGit | Affected
| Fixed in
|
GitHubtortoisegit/tortoisegitpkg:github/tortoisegit/tortoisegitOther 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
If you cannot patch yet, avoid opening or interacting with untrusted Git repositories containing suspicious filenames in TortoiseGitBlame. Exercise caution with local repositories from untrusted sources.
Description
Argument Injection in TortoiseGitBlame via Malicious Git History Filenames Leads to Arbitrary File Write in TortoiseGit