Skip to main content
Mallory
LowPublic exploitVulnerability

CVE-2026-113408: Path Traversal in Git Protocol v2 Unborn HEAD Handling

Published Nov 12, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days24 mentions · peak 9 in a dayToday
CVSS3.3Low · v3.1
EPSS0.26%17th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
IdentifiersCVE-2026-113408CWE-22 · Improper Limitation of a Pathname…

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

1 exploit validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
git-cve-2026-113408-pocThe repository contains a standalone Python exploit fixture, a reproduction README, and a .gitignore excluding generated fixture data and Python caches. poc_server.py creates or validates an empty bare Git repository, enables unborn-ref advertisement, and serves it through ThreadingHTTPServer backed by git http-backend. It forwards Git-Protocol negotiation and rewrites occurrences of symref-target:refs/heads/main into a traversal-bearing target, preserving pkt-line framing and HTTP response lengths. GET and POST requests are supported, with mutation counts exposed in a custom response header and stderr logs. The exploit targets client-side acceptance and subsequent filesystem resolution of an unsafe unborn HEAD. Cloning alone establishes the malicious HEAD; the demonstrated filesystem write requires the user's first commit. The payload writes a commit object ID outside .git rather than executing commands. There are no embedded hooks, reverse shells, credential collection, callbacks, or third-party destinations. A normal clone of the source repository does not reproduce the issue because the malicious advertisement must come from the controlled fixture. The code is functional exploit logic rather than detection-only code, although exploit success and the claimed CVE assignment were not independently verified. Exact affected versions are absent. Binding defaults to loopback but can be changed, and the implementation only warns about non-loopback exposure. Repository URL, revision, and archive size were not provided; empty metadata strings and size_bytes=0 represent unavailable values. The three supplied file sizes total 10,526 bytes, which is not an archive-size measurement.xssdoctor · Disclosed Nov 13, 2026 · python · networkOperational
FAQ

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.
Activity feed

Recent activity

24 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+13 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity7Community discussion across Reddit, Mastodon, and other social sources.