CVE-2023-49569 is a path traversal vulnerability in go-git versions before 5.11.0. A malicious Git server can return crafted responses that cause an affected go-git client to create or modify files outside the intended repository filesystem boundary. The issue affects applications using go-billy's ChrootOS filesystem implementation, which is the default filesystem for the Plain variants of go-git's Open and Clone operations, including PlainClone. Applications using BoundOS or in-memory filesystems are not affected. This is an implementation flaw in go-git and does not affect the upstream Git CLI.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
37 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A go-git flaw in which malicious Git server replies can cause path traversal and remote code execution on go-git clients.
A go-git flaw in which malicious Git server replies can cause path traversal and remote code execution on go-git clients.
Unknown; the advisory lists this CVE but provides no vulnerability description.
A malicious Git server can send crafted replies that cause path traversal and remote code execution on go-git clients.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.