CVE-2026-11968

MEDIUMPre-NVD 5.55.5—
EchelonGraph scoreHIGH confidence

Score 5.5 from GitHub Security Advisory published 2026-06-24. a secondary CVSS source baseline 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Argument Injection in TortoiseGitBlame via Malicious Git History Filenames Leads to Arbitrary File Write in TortoiseGit

CVSS v3
5.5
EG Score
5.5(high)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
2.6%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 25, 2026

Advisory Details (2)

Auto-updated Jun 25, 2026
No patch confirmed yet.
generic

Possible arbitrary file write in TortoiseGitBlame when issuing actions on previous revisions in repository with malicious Git history filenames (#4269) · Issues · TortoiseGit / TortoiseGit · GitLab

https://tortoisegit.org/issue/4269
generic

Properly encode all parameters passed to TortoiseGit tools (7052e3ef) · Commits · TortoiseGit / TortoiseGit · GitLab

https://gitlab.com/tortoisegit/tortoisegit/-/commit/7052e3ef61cd104f8a90fb3dcdfb403cbc8c1773

Vendor Advisories for CVE-2026-11968(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 57× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 03:05 UTCEG score recompute
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-21 15:24 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 14:30 UTCEPSS rescore
  7. 2026-07-19 02:28 UTCEPSS rescore
  8. 2026-07-18 10:04 UTCEPSS rescore
  9. 2026-07-16 17:02 UTCEPSS rescore
  10. 2026-07-16 14:19 UTCGHSA enrichment
  11. 2026-07-15 16:57 UTCEPSS rescore
  12. 2026-07-15 14:00 UTCGHSA enrichment
  13. 2026-07-15 02:00 UTCEPSS rescore
  14. 2026-07-14 13:41 UTCGHSA enrichment
  15. 2026-07-13 22:30 UTCEPSS rescore
  16. 2026-07-13 13:40 UTCGHSA enrichment
  17. 2026-07-13 06:12 UTCEPSS rescore
  18. 2026-07-12 13:38 UTCGHSA enrichment
  19. 2026-07-12 05:46 UTCEPSS rescore
  20. 2026-07-11 13:36 UTCGHSA enrichment
  21. 2026-07-11 08:27 UTCEPSS rescore
  22. 2026-07-10 13:31 UTCGHSA enrichment
  23. 2026-07-09 19:10 UTCEPSS rescore
  24. 2026-07-09 13:29 UTCGHSA enrichment
  25. 2026-07-08 15:15 UTCEPSS rescore
Show 32 more
  1. 2026-07-08 15:15 UTCEPSS rescore
  2. 2026-07-08 13:26 UTCGHSA enrichment
  3. 2026-07-07 13:46 UTCEPSS rescore
  4. 2026-07-07 13:25 UTCGHSA enrichment
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 13:23 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-05 12:55 UTCGHSA enrichment
  9. 2026-07-05 02:30 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-04 12:52 UTCGHSA enrichment
  12. 2026-07-03 12:50 UTCGHSA enrichment
  13. 2026-07-02 12:07 UTCGHSA enrichment
  14. 2026-07-01 15:06 UTCEPSS rescore
  15. 2026-07-01 15:06 UTCEPSS rescore
  16. 2026-07-01 12:02 UTCGHSA enrichment
  17. 2026-06-30 23:22 UTCEPSS rescore
  18. 2026-06-30 12:00 UTCGHSA enrichment
  19. 2026-06-29 14:06 UTCEPSS rescore
  20. 2026-06-29 11:59 UTCGHSA enrichment
  21. 2026-06-28 14:07 UTCEPSS rescore
  22. 2026-06-28 11:57 UTCGHSA enrichment
  23. 2026-06-28 04:56 UTCEPSS rescore
  24. 2026-06-28 04:56 UTCEPSS rescore
  25. 2026-06-27 11:56 UTCGHSA enrichment
  26. 2026-06-27 03:08 UTCEPSS rescore
  27. 2026-06-26 11:55 UTCGHSA enrichment
  28. 2026-06-25 13:49 UTCEPSS rescore
  29. 2026-06-25 11:53 UTCGHSA enrichment
  30. 2026-06-24 14:05 UTCEPSS rescore
  31. 2026-06-24 11:51 UTCEG score recompute
  32. 2026-06-24 11:50 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-11968?
CVE-2026-11968 is a medium vulnerability published on June 24, 2026. Argument Injection in TortoiseGitBlame via Malicious Git History Filenames Leads to Arbitrary File Write in TortoiseGit
When was CVE-2026-11968 disclosed?
CVE-2026-11968 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-11968 actively exploited?
CVE-2026-11968 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-11968?
CVE-2026-11968 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-11968?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-11968, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-11968

Explore →

Is Your Infrastructure Affected by CVE-2026-11968?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs