CVE-2026-11968Public exploit

Arbitrary file write via injected Blame arguments

Published Jun 24, 2026 · Updated Jun 24, 2026

Argument injection in TortoiseGit allows context-dependent attackers to write arbitrary files via malicious Git history filenames. TortoiseGitBlame places a historical filename on a TortoiseGitProc command line without neutralizing delimiters, allowing embedded /command, /revision, and /savepath tokens to replace intended arguments. Exploitation requires a victim to clone the malicious repository and select Blame previous or Diff with previous, after which a chosen Git blob is written to an attacker-selected path.

CVSS severity5.5
Medium
EPSS probability0.18%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Argument injection in TortoiseGit allows context-dependent attackers to write arbitrary files via malicious Git history filenames. TortoiseGitBlame places a historical filename on a TortoiseGitProc command line without neutralizing delimiters, allowing embedded /command, /revision, and /savepath tokens to replace intended arguments. Exploitation requires a victim to clone the malicious repository and select Blame previous or Diff with previous, after which a chosen Git blob is written to an attacker-selected path.

The record

CVE
CVE-2026-11968
Published
Jun 24, 2026
Updated
Jun 24, 2026
Vendor
TortoiseGit
Product
TortoiseGit
Classifications
CWE-88, T1204.002
Attack vector
local
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jun 24, 2026CVE publishedPublication date reported by the CVE source.
  2. Jun 24, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=1.8.10.0 <2.19.0

What conditions does exploitation require?

Attack vectorlocal
Required privilegesunauthenticated

What is affected?

TortoiseGit · TortoiseGitversion=1.8.10.0 <2.19.0

Published CVSS scores

5.5GitLab Inc.CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-88Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')
T1204.002User Execution: Malicious File

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo