CVE-2023-25652
No exploitation reported by the sources we read.
- Published2023-04-25
- Fixed in2.39.3 · 2.38.5 · 2.37.7 · 2.36.6 · 2.35.8 · 2.34.8
- WeaknessCWE-22
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « 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 is a revision control system. Prior to versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1, by feeding specially crafted input to `git apply --reject`, a path outside the working tree can be overwritten with partially controlled contents (corresponding to the rejected hunk(s) from the given patch). A fix is available in versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1. As a workaround, avoid using `git apply` with `--reject` when applying patches from an untrusted source. Use `git apply --stat` to inspect a patch before applying; avoid applying one that create a conflict where a link corresponding to the `*.rej` file exists.
Timeline
dates in UTC- 2023-04-2520:15CVE publishedNVD
- 2026-10-2319:23EPSS crossed 10 %FIRST EPSS
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2023-25652?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2023-25652?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2.39 | ≥ 2.39.0, < 2.39.3 | 2.39.3 | NVD |
| 2.38 | ≥ 2.38.0, < 2.38.5 | 2.38.5 | NVD |
| 2.37 | ≥ 2.37.0, < 2.37.7 | 2.37.7 | NVD |
| 2.36 | ≥ 2.36.0, < 2.36.6 | 2.36.6 | NVD |
| 2.35 | ≥ 2.35.0, < 2.35.8 | 2.35.8 | NVD |
| 2.34 | ≥ 2.34.0, < 2.34.8 | 2.34.8 | NVD |
| 2.33 | ≥ 2.33.0, < 2.33.8 | 2.33.8 | NVD |
| 2.32 | ≥ 2.32.0, < 2.32.7 | 2.32.7 | NVD |
| 2.31 | ≥ 2.31.0, < 2.31.8 | 2.31.8 | NVD |
| 2.30 | < 2.30.9 | 2.30.9 | NVD |
| 2.40 | = 2.40.0 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 37.x | = 37 | no fix published | NVD |
| 38.x | = 38 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Git-scm git to 2.39.3 · 2.38.5 · 2.37.7 · 2.36.6 · 2.35.8 · 2.34.8 · 2.33.8 · 2.32.7
Advisories and patches
- github.comPatch
- github.comPatch
- github.comVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
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-04-25
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2023-25652?
Is CVE-2023-25652 actively exploited?
What is the CVSS score for CVE-2023-25652?
Hear about the next vulnerability in your software
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 ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.