Skip to main content
VulnerabilityPublished

CVE-2026-113408: Git · Path Traversal

Source GCVE Database

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

Not known to be exploited · CVSS 3.3 Low.

Data as of 12 Nov 2026, 10:19 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
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 11 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
GitGitAffected
  • 2.50.1 – 2.56.0
7 affected builds
Fixed in–

AI-suggested

Until a fix is available, users should exercise caution when cloning and committing to untrusted repositories to avoid potential exploitation.

Description

A path traversal vulnerability in Git allows an attacker to write to arbitrary files by cloning and committing to a malicious repository. This flaw could be triggered by a user interacting with a crafted repository, potentially leading to limited integrity impact without confidentiality or availability effects.

References

Community reviews

Loading reviews…