Skip to main content
Mallory
MediumVulnerability

CVE-2026-114466: Arbitrary File Read and Write in Git fast-import

Published Nov 12, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days23 mentions · peak 7 in a dayToday
CVSS4.4Medium · v3.1
EPSS0.23%14th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-114466CWE-73

CVE-2026-114466 is an arbitrary filesystem access vulnerability in Git's fast-import functionality when processing untrusted import streams. The rewrite-submodules-from and rewrite-submodules-to features and the export-pack-edges option were not classified as unsafe despite accepting arbitrary filesystem paths. The submodule-rewriting features can read files outside the repository and disclose their contents through parsing error messages. The export-pack-edges option can create files or append data to existing files. Patched releases reject these stream-supplied features by default unless the caller explicitly enables --allow-unsafe-features.

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 compromises confidentiality by exposing files readable by the Git process and compromises integrity by creating files or appending attacker-controlled data to writable files outside the repository. Filesystem access is limited by the operating-system permissions of the account running Git. Code execution, privilege escalation, and availability impacts are not established for this vulnerability.

Mitigation

If you can’t patch tonight, do this now.

Until patched, do not process fast-import streams from untrusted sources. On patched installations, leave unsafe features disabled and permit --allow-unsafe-features only when the stream generator and its input are trusted. Running import jobs under a dedicated, least-privileged account with restricted filesystem access can reduce the scope of accessible files but does not replace patching.

Remediation

Patch, then assume compromise.

Install Git 2.56.1 or the patched release appropriate to the installed maintenance 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 explicitly containing the CVE-2026-114466 fix. Update applications and automation systems that bundle their own Git executable. The fix gates the affected stream-supplied features behind --allow-unsafe-features; do not enable this option for untrusted streams.

Public exploits

Exploits

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

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
FAQ

Frequently asked questions

Is CVE-2026-114466 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-114466 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-114466?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-114466.
Is there a patch for CVE-2026-114466?
Install Git 2.56.1 or the patched release appropriate to the installed maintenance 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 explicitly containing the CVE-2026-114466 fix.
How severe is CVE-2026-114466?
CVE-2026-114466 has a CVSS v3.1 score of 4.4 (Medium) and an EPSS score of 0.23% (14th percentile) as of Nov 17, 2026.
Activity feed

Recent activity

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

View more in app →
+15 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 activity4Community discussion across Reddit, Mastodon, and other social sources.