CVE-2026-113408: Path Traversal in Git Protocol v2 Unborn HEAD Handling
CVE-2026-113408 is a path-traversal vulnerability in Git's handling of server-advertised references when cloning an empty repository over protocol v2. Git fails to validate the advertised unborn HEAD symbolic-reference target, allowing a malicious server to supply a branch name containing traversal components. With the files reference backend, a subsequent reference update, such as one performed by git commit, can resolve the malicious target outside the intended reference directory and write to an unintended file.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation permits unintended file creation or modification outside Git's reference directory, subject to the filesystem permissions of the Git process. This compromises filesystem integrity and may damage repository or other writable data. Arbitrary-content writes, code execution, and information disclosure are not established for this vulnerability.
Mitigation
If you can’t patch tonight, do this now.
Until patched, clone only from trusted servers. Avoid cloning attacker-controlled or otherwise untrusted empty repositories and performing subsequent commits or reference updates in them. These precautions do not replace installing the security update.
Remediation
Patch, then assume compromise.
Upgrade to Git 2.56.1 or the patched maintenance release for the installed series: 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1, or 2.55.1. Alternatively, install a vendor package containing the backported fix. Update applications and automation systems that bundle their own Git executable. The fix validates HEAD symbolic-reference targets and other reference names and symbolic-reference targets received over protocol v2.
Exploits
1 exploit validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit.
Frequently asked questions
- Is CVE-2026-113408 exploited in the wild?
- As of Nov 17, 2026, Mallory has no reports of CVE-2026-113408 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-113408?
- Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-113408, the earliest disclosed Nov 13, 2026.
- Is there a patch for CVE-2026-113408?
- Upgrade to Git 2.56.1 or the patched maintenance release for the installed series: 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1, or 2.55.1. Alternatively, install a vendor package containing the backported fix.
- How severe is CVE-2026-113408?
- CVE-2026-113408 has a CVSS v3.1 score of 3.3 (Low) and an EPSS score of 0.26% (17th percentile) as of Nov 17, 2026.
Recent activity
24 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.