Git · weakness class
File and Path Handling
8 CVEs
Every dot is a CVE in what this vendor ships; the named ones are the most at risk.
- likely to be exploited
- 3
Every one of the 8 is a mark on the map. Named now: 1 to 8, most at risk first.
- malicious repositories can execute remote code while cloning
- "git apply --reject" partially-controlled arbitrary file write
- Git's recursive clones on case-insensitive filesystems that support symlinks are susceptible to Remote Code Execution
- Git vulnerable to Remote Code Execution while cloning special-crafted local repositories
- Git's `git apply` overwriting paths outside the working tree
- Git's protections for cloning untrusted repositories can be bypassed
- Git vulnerable to local clone-based data exfiltration with non-local transports
- Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in Git
CWE-222 articles2 articles this week: Git fixes six flaws enabling code execution in recursive clones
exploited in the wildcheck availableringed, named or not: CyberSIXT has reported on it
Zoom in on the map and the dots under the middle of it are named where they are.
Data as of 2026-11-14. CVE List through 2026-11-14 · EPSS of 2026-11-14 · CISA KEV checked 2026-11-14. Sources: the CVE List, CISA KEV, EPSS, NVD, nuclei templates and public bug bounty data. Use this via MCP