Skip to main content
VulnerabilityPublished

CVE-2026-113408: Git · Path Traversal

Affects gitSource GCVE Database

0
Compare
Authoritative record:CVE-2026-113408· Low 3.3

Not known to be exploited · CVSS 3.3 Low : upgrade to 2.56.1-r0 when convenient.

Data as of 20 Nov 2026, 03:08 UTC

CVSS 3.1 base score
3.3Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitLab)CVSS 3.13.3
Patch
Available – fixed in 2.56.1-r0
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 19 Nov 2026.

What to do

Upgrade git to 2.56.1-r0.

Affected software

ProductAffectedFixed in
CleanStartgitpkg:apk/cleanstart/gitOther threatsAffected
  • <2.56.1-r0
Fixed in
  • 2.56.1-r0

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

AI-suggested

Upgrade Git to version 2.56.1-r0 or later to apply the official fix for this vulnerability. Since a patch is available and the issue is fixed in this version, no additional mitigation steps are necessary.

Description

A path traversal vulnerability in Git allows an attacker to write to arbitrary files by cloning and committing to a malicious repository. This issue affects Git versions prior to 2.56.1-r0 and has a low severity rating with a CVSS score of 3.3. The vulnerability has been fixed in version 2.56.1-r0.

References

Community reviews

Loading reviews…