CVE
Git path traversal lets attackers write files in repo cloning
- Exploited
- Public exploit code, no confirmed attacks
- Fix
- See vendor advisory
- Who is exposed
- Not reported
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- First public exploit on GitHub Nov 13
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.26% · 17th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 30/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
Summary
Git, the version control software, has a path traversal flaw that lets a local attacker write to arbitrary files on a user's system. The attacker needs the victim to clone and commit to a malicious repository, so the victim has to take action for the attack to work.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Path traversal in Git allows writing to arbitrary file via cloning and committing to bad repository
cve.now Index
- Exploitation22/40Public exploit on Exploit-DB or GitHub · Unknown: No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity3.3/10CVSS 3.3
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 52 if advisories confirm default setups are exposed
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-113408 (Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in Git), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-113408 (entry last updated 2026-11-12):
Affected:
- Git Git: versions 2.50.1, 2.51.2, 2.52.0, 2.53.0, 2.54.0, 2.55.0, 2.56.0
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-113408 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-113408 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://gitlab.com/gitlab-org/git/-/work_items/809
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-113408
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-113408"}.Timeline
- CVE published
- First seen by cve.now1 day
- Exploit code on GitHub
xssdoctor/git-cve-2026-113408-poc
Affected versions
- Git Git
2.50.1, 2.51.2, 2.52.0, 2.53.0, 2.54.0, 2.55.0, 2.56.0
Evidence 4
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Public exploit code · 1
Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
- Exploit
Other links · 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-113408
Is CVE-2026-113408 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. Public exploit code exists (a proof of concept on GitHub).Source: cve.now feed data
Which versions are affected by CVE-2026-113408?
Git: versions 2.50.1, 2.51.2, 2.52.0, 2.53.0, 2.54.0 and 2 more.Source: cve.now feed data