Git's `git apply` overwriting paths outside the working tree
Noroxi assessment
Priority: Monitor (action score 30/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.1% (FIRST EPSS); higher than 65.6% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: git (AlmaLinux:8) 2.39.3-1.el8_8; git-all (AlmaLinux:8) 2.39.3-1.el8_8; git-core (AlmaLinux:8) 2.39.3-1.el8_8.
Low priority for now. Upgrade to git (AlmaLinux:8) 2.39.3-1.el8_8; git-all (AlmaLinux:8) 2.39.3-1.el8_8; git-core (AlmaLinux:8) 2.39.3-1.el8_8 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Git, a revision control system, is vulnerable to path traversal prior to versions 2.39.2, 2.38.4, 2.37.6, 2.36.5, 2.35.7, 2.34.7, 2.33.7, 2.32.6, 2.31.7, and 2.30.8. By feeding a crafted input to `git apply`, a path outside the working tree can be overwritten as the user who is running `git apply`. A fix has been prepared and will appear in v2.39.2, v2.38.4, v2.37.6, v2.36.5, v2.35.7, v2.34.7, v2.33.7, v2.32.6, v2.31.7, and v2.30.8. As a workaround, use `git apply --stat` to inspect a patch before applying; avoid applying one that creates a symbolic link and then creates a file beyond the symbolic link.
- Published
- Feb 14, 2023
- Updated
- Oct 8, 2026
- EPSS
- 1.1% · 66th percentile
- CWE
- CWE-22
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.5
- CNA · GitHub_M
- 6.2
- 1.3 point gap
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| git-scm | git | cpe:2.3:a:git-scm:git |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- git-scm gitbefore 2.30.8
- git-scm git2.31.0 and later · before 2.31.7
- git-scm git2.32.0 and later · before 2.32.6
- git-scm git2.33.0 and later · before 2.33.7
- git-scm git2.34.0 and later · before 2.34.7
- git-scm git2.35.0 and later · before 2.35.7
- git-scm git2.36.0 and later · before 2.36.5
- git-scm git2.37.0 and later · before 2.37.6
- git-scm git2.38.0 and later · before 2.38.4
- git-scm git2.39.0 and later · before 2.39.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
git git
- >= 2.39.0, < 2.39.2, >= 2.38.0, < 2.38.4, >= 2.37.0, < 2.37.6, >= 2.36.0, < 2.36.5, >= 2.35.0, < 2.35.7, >= 2.34.0, < 2.34.7, >= 2.33.0, < 2.33.7, >= 2.32.0, < 2.32.6, >= 2.31.0, < 2.31.7, < 2.30.8affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | git | before 2.39.3-1.el8_8 | 2.39.3-1.el8_8 |
| AlmaLinux:8 | git-all | before 2.39.3-1.el8_8 | 2.39.3-1.el8_8 |
| AlmaLinux:8 | git-core | before 2.39.3-1.el8_8 | 2.39.3-1.el8_8 |
| AlmaLinux:8 | git-core-doc | before 2.39.3-1.el8_8 | 2.39.3-1.el8_8 |
| AlmaLinux:8 | git-credential-libsecret | before 2.39.3-1.el8_8 | 2.39.3-1.el8_8 |
| AlmaLinux:8 | git-daemon | before 2.39.3-1.el8_8 | 2.39.3-1.el8_8 |
| AlmaLinux:8 | git-email | before 2.39.3-1.el8_8 | 2.39.3-1.el8_8 |
| AlmaLinux:8 | git-gui | before 2.39.3-1.el8_8 | 2.39.3-1.el8_8 |
| AlmaLinux:8 | git-instaweb | before 2.39.3-1.el8_8 | 2.39.3-1.el8_8 |
| AlmaLinux:8 | git-subtree | before 2.39.3-1.el8_8 | 2.39.3-1.el8_8 |
| AlmaLinux:8 | git-svn | before 2.39.3-1.el8_8 | 2.39.3-1.el8_8 |
| AlmaLinux:8 | gitk | before 2.39.3-1.el8_8 | 2.39.3-1.el8_8 |
| AlmaLinux:8 | gitweb | before 2.39.3-1.el8_8 | 2.39.3-1.el8_8 |
| AlmaLinux:8 | perl-Git | before 2.39.3-1.el8_8 | 2.39.3-1.el8_8 |
| AlmaLinux:8 | perl-Git-SVN | before 2.39.3-1.el8_8 | 2.39.3-1.el8_8 |
| AlmaLinux:9 | git | before 2.39.3-1.el9_2 | 2.39.3-1.el9_2 |
| AlmaLinux:9 | git-all | before 2.39.3-1.el9_2 | 2.39.3-1.el9_2 |
| AlmaLinux:9 | git-core | before 2.39.3-1.el9_2 | 2.39.3-1.el9_2 |
| AlmaLinux:9 | git-core-doc | before 2.39.3-1.el9_2 | 2.39.3-1.el9_2 |
| AlmaLinux:9 | git-credential-libsecret | before 2.39.3-1.el9_2 | 2.39.3-1.el9_2 |
| AlmaLinux:9 | git-daemon | before 2.39.3-1.el9_2 | 2.39.3-1.el9_2 |
| AlmaLinux:9 | git-email | before 2.39.3-1.el9_2 | 2.39.3-1.el9_2 |
| AlmaLinux:9 | git-gui | before 2.39.3-1.el9_2 | 2.39.3-1.el9_2 |
| AlmaLinux:9 | git-instaweb | before 2.39.3-1.el9_2 | 2.39.3-1.el9_2 |
+81
Same product
git-scm: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-17456Git before 2.14.5, 2.15.x before 2.15.3, 2.16.x before 2.16.5, 2.17.x before 2.17.2, 2.18.x before 2.18.1, and 2.19.x before 2.19.1 allows r68This week
- CVE-2025-48384Git allows arbitrary code execution through broken config quotingKEV63This week
- CVE-2017-1000117A malicious third-party can give a crafted "ssh://..." URL to an unsuspecting victim, and an attempt to visit the URL can result in any prog58Plan
- CVE-2021-21300malicious repositories can execute remote code while cloning57Plan
- CVE-2022-23521gitattributes parsing integer overflow in git56Plan
- CVE-2022-41903Integer overflow in `git archive`, `git log --format` leading to RCE in git52Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:git | 2.39.3-1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:git-all | 2.39.3-1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:git-core | 2.39.3-1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:git-core-doc | 2.39.3-1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:git-credential-libsecret | 2.39.3-1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:git-daemon | 2.39.3-1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:git-email | 2.39.3-1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:git-gui | 2.39.3-1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:git-instaweb | 2.39.3-1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:git-subtree | 2.39.3-1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:git-svn | 2.39.3-1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:gitk | 2.39.3-1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| alpine:git | 2.32.6-r0 · Alpine:v3.14 | Package registry (OSV) |
| debian:git | 1:2.39.2-1 · Debian:12 | Package registry (OSV) |
| opensuse:git | 2.26.2-150000.47.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| red hat:git | 0:2.39.3-1.el9_2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:git-all | 0:2.39.3-1.el9_2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:git-core | 0:2.39.3-1.el9_2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:git-core-debuginfo | 0:2.39.3-1.el9_2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:git-core-doc | 0:2.39.3-1.el9_2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:git-credential-libsecret | 0:2.39.3-1.el9_2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:git-credential-libsecret-debuginfo | 0:2.39.3-1.el9_2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:git-daemon | 0:2.39.3-1.el9_2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:git-daemon-debuginfo | 0:2.39.3-1.el9_2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:git-debuginfo | 0:2.39.3-1.el9_2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:git-debugsource | 0:2.39.3-1.el9_2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:git-email | 0:2.39.3-1.el9_2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| rocky linux:git | 0:2.39.3-1.el8_8 · Rocky Linux:8 | Package registry (OSV) |
| suse:git | 2.26.2-150000.47.1 · SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×2
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:1 | 2023-09-07 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-05-16 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+204 d
- TodayOct 13, 2026+1337 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
nvd-primary
Root cause
A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.
The bug in code
The whole CWE-22 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const file = path.join(ROOT, req.query.name);res.sendFile(file);Fixed
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) { return res.sendStatus(400);}res.sendFile(file);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Path TraversalCAPEC-126likelihood: High · Very High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
ATT&CK techniques
—
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.