Skip to content
Noroxi
CVE-2023-25652· NVD / CVE Program· CNA GitHub_M

"git apply --reject" partially-controlled arbitrary file write

Noroxi assessment

Priority: Plan (action score 46/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 51.8% (FIRST EPSS); higher than 98.9% 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.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Add it to your regular patch cycle. 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

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
Apr 25, 2023
Updated
Jun 17, 2026
EPSS
51.8% · 98th percentile

Report tools

JSON

Action score

46

Plan

Add it to your regular patch cycle.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
16 / 30 · 51.8%

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
7.5
agree

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
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-25652

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

VendorProduct
git-scmgit
fedoraprojectfedora

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • fedoraproject fedora37
  • fedoraproject fedora38
  • git-scm git2.32.0 and later · before 2.32.7
  • git-scm git2.33.0 and later · before 2.33.8
  • git-scm git2.34.0 and later · before 2.34.8
  • git-scm git2.35.0 and later · before 2.35.8
  • git-scm gitbefore 2.30.9
  • git-scm git2.37.0 and later · before 2.37.7
  • git-scm git2.38.0 and later · before 2.38.5
  • git-scm git2.39.0 and later · before 2.39.3
  • git-scm git2.36.0 and later · before 2.36.6
  • git-scm git2.31.0 and later · before 2.31.8
  • git-scm git2.40.0

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.30.9, >= 2.31.0, < 2.31.8, >= 2.32.0, < 2.32.7, >= 2.33.0, < 2.33.8, >= 2.34.0, < 2.34.8, >= 2.35.0, < 2.35.8, >= 2.36.0, < 2.36.6, >= 2.37.0, < 2.37.7, >= 2.38.0, < 2.38.5, >= 2.39.0, < 2.39.3, >= 2.40.0, < 2.40.1affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8gitbefore 2.39.3-1.el8_82.39.3-1.el8_8
AlmaLinux:8git-allbefore 2.39.3-1.el8_82.39.3-1.el8_8
AlmaLinux:8git-corebefore 2.39.3-1.el8_82.39.3-1.el8_8
AlmaLinux:8git-core-docbefore 2.39.3-1.el8_82.39.3-1.el8_8
AlmaLinux:8git-credential-libsecretbefore 2.39.3-1.el8_82.39.3-1.el8_8
AlmaLinux:8git-daemonbefore 2.39.3-1.el8_82.39.3-1.el8_8
AlmaLinux:8git-emailbefore 2.39.3-1.el8_82.39.3-1.el8_8
AlmaLinux:8git-guibefore 2.39.3-1.el8_82.39.3-1.el8_8
AlmaLinux:8git-instawebbefore 2.39.3-1.el8_82.39.3-1.el8_8
AlmaLinux:8git-subtreebefore 2.39.3-1.el8_82.39.3-1.el8_8
AlmaLinux:8git-svnbefore 2.39.3-1.el8_82.39.3-1.el8_8
AlmaLinux:8gitkbefore 2.39.3-1.el8_82.39.3-1.el8_8
AlmaLinux:8gitwebbefore 2.39.3-1.el8_82.39.3-1.el8_8
AlmaLinux:8perl-Gitbefore 2.39.3-1.el8_82.39.3-1.el8_8
AlmaLinux:8perl-Git-SVNbefore 2.39.3-1.el8_82.39.3-1.el8_8
AlmaLinux:9gitbefore 2.39.3-1.el9_22.39.3-1.el9_2
AlmaLinux:9git-allbefore 2.39.3-1.el9_22.39.3-1.el9_2
AlmaLinux:9git-corebefore 2.39.3-1.el9_22.39.3-1.el9_2
AlmaLinux:9git-core-docbefore 2.39.3-1.el9_22.39.3-1.el9_2
AlmaLinux:9git-credential-libsecretbefore 2.39.3-1.el9_22.39.3-1.el9_2
AlmaLinux:9git-daemonbefore 2.39.3-1.el9_22.39.3-1.el9_2
AlmaLinux:9git-emailbefore 2.39.3-1.el9_22.39.3-1.el9_2
AlmaLinux:9git-guibefore 2.39.3-1.el9_22.39.3-1.el9_2
AlmaLinux:9git-instawebbefore 2.39.3-1.el9_22.39.3-1.el9_2

+96

Other 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 r
    68This week
  • CVE-2025-48384Git allows arbitrary code execution through broken config quotingKEV
    63This week
  • CVE-2021-21300malicious repositories can execute remote code while cloning
    60This week

Published before and after this one in the same product

  • ← EarlierCVE-2023-22490Feb 14, 2023 · Git vulnerable to local clone-based data exfiltration with non-local transports
    22Monitor
  • ← EarlierCVE-2023-23946Feb 14, 2023 · Git's `git apply` overwriting paths outside the working tree
    30Monitor
  • Later →CVE-2023-29007Apr 25, 2023 · Arbitrary configuration injection via `git submodule deinit`
    33Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
almalinux:git2.39.3-1.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:git-all2.39.3-1.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:git-core2.39.3-1.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:git-core-doc2.39.3-1.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:git-credential-libsecret2.39.3-1.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:git-daemon2.39.3-1.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:git-email2.39.3-1.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:git-gui2.39.3-1.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:git-instaweb2.39.3-1.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:git-subtree2.39.3-1.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:git-svn2.39.3-1.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:gitk2.39.3-1.el9_2 · AlmaLinux:9Package registry (OSV)
alpine:git2.32.7-r0 · Alpine:v3.14Package registry (OSV)
debian:git1:2.39.5-0+deb12u1 · Debian:12Package registry (OSV)
opensuse:git2.35.3-150300.10.27.1 · openSUSE:Leap 15.4Package registry (OSV)
red hat:git0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstreamPackage registry (OSV)
red hat:git-all0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstreamPackage registry (OSV)
red hat:git-core0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstreamPackage registry (OSV)
red hat:git-core-debuginfo0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstreamPackage registry (OSV)
red hat:git-core-doc0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstreamPackage registry (OSV)
red hat:git-daemon0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstreamPackage registry (OSV)
red hat:git-daemon-debuginfo0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstreamPackage registry (OSV)
red hat:git-debuginfo0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstreamPackage registry (OSV)
red hat:git-debugsource0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstreamPackage registry (OSV)
red hat:git-email0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstreamPackage registry (OSV)
red hat:git-gui0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstreamPackage registry (OSV)
red hat:git-instaweb0:2.18.4-3.el8_1 · Red Hat:rhel_e4s:8.1::appstreamPackage registry (OSV)
rocky linux:git0:2.39.3-1.el8_8 · Rocky Linux:8Package registry (OSV)
suse:git2.35.3-150300.10.27.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP4Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

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.

No dated events beyond publication.

EPSS, last 120 days

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.

Finders, 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).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

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

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.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const file = path.join(ROOT, req.query.name);res.sendFile(file);

Fixed

ts
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) {  return res.sendStatus(400);}res.sendFile(file);

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records