Skip to main content
Public proof of conceptFix available

CVE-2023-23946

A public proof of concept exists; no exploitation attested.

  • Published2023-02-14
  • Fixed in2.39.2 · 2.38.4 · 2.37.6 · 2.36.5 · 2.35.7 · 2.34.7
  • WeaknessCWE-22

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2023-02-1420:15CVE publishedNVD
  2. 2026-10-2319:23First public proof of conceptPoC-in-GitHub

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2023-23946?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2023-23946?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Git-scm git
BranchAffectedFixed in
2.39≥ 2.39.0, < 2.39.22.39.2
2.38≥ 2.38.0, < 2.38.42.38.4
2.37≥ 2.37.0, < 2.37.62.37.6
2.36≥ 2.36.0, < 2.36.52.36.5
2.35≥ 2.35.0, < 2.35.72.35.7
2.34≥ 2.34.0, < 2.34.72.34.7
2.33≥ 2.33.0, < 2.33.72.33.7
2.32≥ 2.32.0, < 2.32.62.32.6
2.31≥ 2.31.0, < 2.31.72.31.7
2.30< 2.30.82.30.8

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • gitAlmaLinux:9all versions · fixed in 2.39.3-1.el9_2and 14 other packages
  • gitAlmaLinux:8all versions · fixed in 2.39.3-1.el8_8and 14 other packages

Full record on NVD

Fix

  1. Update Git-scm git to 2.39.2 · 2.38.4 · 2.37.6 · 2.36.5 · 2.35.7 · 2.34.7 · 2.33.7 · 2.32.6

Advisories and patches

Detection

read 2026-10-23 19:23 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
2 repositories, unverifiedbruno-1337/CVE-2023-23946-POCtralsesec/CVE-2023-23946
PoC-in-GitHub

Sources

  • CISA-ADPSSVC decisionnone2026-10-08
  • OpenCVESSVC decisionnone—
  • CNACVSS 3.16.2read 2026-10-23
  • NVDCVSS 3.17.5read 2026-10-23
  • CNAweakness (CWE)CWE-22read 2026-10-23
  • NVDweakness (CWE)CWE-22read 2026-10-23
  • FIRST EPSSEPSS score1.1 %2026-10-23
  • PoC-in-GitHubproof of concept2read 2026-10-23
  • OSVaffected packages—

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Published
2023-02-14
Last Modified
2026-10-08
NVD status
Modified

Frequently asked questions

What is CVE-2023-23946?

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.

Is CVE-2023-23946 actively exploited?

Active exploitation of CVE-2023-23946 has not been confirmed. Its EPSS score was 1.1% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2023-23946?

CVE-2023-23946 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N.

Running git? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database