CVE-2025-48384: Git Git

Should you act?

Exploited: patch now if you run it

CISA has confirmed exploitation in the wild. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

Yes, if you run Git Git. CISA added this CVE to its Known Exploited Vulnerabilities catalog on 2025-08-25, which means there is reliable evidence of exploitation in the wild. US federal agencies must remediate by 2025-09-15; treat that as the outer limit, not the target.
EPSS 4.4%, percentile 91: FIRST’s model estimates a 4.4% chance of exploitation activity in the next 30 days, higher than 91% of all scored CVEs (elevated). EPSS is a probability, not a verdict.
Needs an account (low (any account)). Exposure depends on who can log in.

What it is

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.

CISA’s summary

Git contains a link following vulnerability that stems from Git’s inconsistent handling of carriage return characters in configuration files.

Weakness type: CWE-436, CWE-59.

Product: Git Git · Assigned by: GitHub_M · Published: 2025-07-08

Affected and fixed versions

Vendor	Product	Affected versions (per CVE record)
git	git	< 2.43.7, >= 2.44.0-rc0, < 2.44.4, >= 2.45.0-rc0, < 2.45.4, >= 2.46.0-rc0, < 2.46.4, >= 2.47.0-rc0, < 2.47.3, >= 2.48.0-rc0, < 2.48.2, >= 2.49.0-rc0, < 2.49.1, >= 2.50.0-rc0, < 2.50.1

Severity scores

Scored by	CVSS	Score	Vector
GitHub_M	3.1	8.1 High	`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H`

Attack vector: network (remotely reachable)
Attack complexity: high (needs special conditions)
Privileges required: low (any account)
User interaction: required (a user must click/open something)
Scope: changed (can affect other components)

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

CISA KEV: added 2025-08-25; federal due date 2025-09-15. Known ransomware use: Unknown.
CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
CISA SSVC assessment: exploitation active, automatable no, technical impact total.
FIRST EPSS (model of 2026-10-21): 4.38% probability of exploitation activity in the next 30 days; percentile 91.

Timeline

2025-07-08 — CVE record published by GitHub_M
2025-08-25 — Added to CISA’s Known Exploited Vulnerabilities catalog
2025-09-15 — CISA remediation deadline for US federal agencies
2026-02-26 — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Other references from the CVE record and advisory

lists.debian.org lists.debian.org
seclists.org seclists.org
openwall.com openwall.com

All exploited Git vulnerabilities · Today’s Security Digest