CVE-2025-48384
Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals. When reading a config value, Git strips any trailing carriage return and line feed (CRLF). When writing a config entry, values with a trailing CR are not quoted, causing the CR to be lost when the config is later read. When initializing a submodule, if the submodule path contains a trailing CR, the altered path is read resulting in the submodule being checked out to an incorrect location. If a symlink exists that points the altered path to the submodule hooks directory, and the submodule contains an executable post-checkout hook, the script may be unintentionally executed after checkout. This vulnerability is fixed in v2.43.7, v2.44.4, v2.45.4, v2.46.4, v2.47.3, v2.48.2, v2.49.1, and v2.50.1.
do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? No. The vulnerability involves Git reading and writing configuration values and initializing submodules on the local filesystem. It requires local access to manipulate submodule paths and symlinks, so it is not triggered via network requests and cannot be filtered by a web application firewall.
Also consider: patch
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2025-48384 being exploited?
Yes. CVE-2025-48384 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2025-48384?
CVE-2025-48384 is rated High with a CVSS score of 8.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-48384?
Yes. A fix has been recorded for CVE-2025-48384. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-48384 affect?
CVE-2025-48384 affects git-scm:git, debian:debian_linux, apple:xcode. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected< 2.43.7
- affected>= 2.44.0-rc0 and < 2.44.4
- affected>= 2.45.0-rc0 and < 2.45.4
- affected>= 2.46.0-rc0 and < 2.46.4
- affected>= 2.47.0-rc0 and < 2.47.3
- affected>= 2.48.0-rc0 and < 2.48.2
- affected>= 2.49.0-rc0 and < 2.49.1
- affected>= 2.50.0-rc0 and < 2.50.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
public exploits
Unvetted proof-of-concept code on GitHub: 42 GitHub proofs of concept
- acheong08/CVE-2025-48384 · 52 ★
- liamg/CVE-2025-48384 · 21 ★
- vinieger/vinieger-CVE-2025-48384-Dockerfile · 1 ★
- IK-20211125/CVE-2025-48384 · 1 ★
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- total
Assessed by CISA 26 Aug 2025 (SSVC 2.0.3).
timeline
- 8 Jul 2025First proof-of-concept repository on GitHub (unvetted)
- 8 Jul 2025Published · 1 day later
- 25 Aug 2025Added to CISA KEV (exploited in the wild) · 47 days later
- 26 Aug 2025CISA SSVC assessment: exploitation active · 1 day later
- 15 Sept 2025CISA remediation due date (US federal agencies) · 20 days later
- 26 Feb 2026CVE record last updated · 165 days (about 6 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 249 days (about 8 months) later
also known as
- Linkgithub.com /git/git/security/advisories/GHSA-vwqx-4fm8-6qc9
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-48384
- Linklists.debian.org /debian-lts-announce/2025/10/msg00003.html
- Linkseclists.org /fulldisclosure/2025/Sep/60
- Linkopenwall.com /lists/oss-security/2025/07/08/4
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- OSV: advisory aliases and downstream package versions
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.