CVE-2025-48384

CVE-2025-48384 is a high-severity vulnerability in Git-scm Git with a CVSS 3.x base score of 8.0. It is listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, confirming it has been exploited in the wild (added 2025-08-25). The underlying weakness is classified as CWE-59.

Key facts

Description

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.

Frequently asked questions

What is 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.
How severe is CVE-2025-48384?
CVE-2025-48384 has a CVSS 3.x base score of 8.0, rated high severity. It is exploitable over network with high attack complexity, requires low privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2025-48384 being actively exploited?
Yes. CVE-2025-48384 is on CISA's Known Exploited Vulnerabilities (KEV) catalog, added on 2025-08-25, which means active exploitation has been confirmed. It should be prioritised for remediation.
What products are affected by CVE-2025-48384?
CVE-2025-48384 primarily affects Git-scm Git. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2025-48384?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Because this CVE is known to be actively exploited, treat remediation as urgent — CISA KEV typically sets a short remediation deadline.
Does CVE-2025-48384 have an EU (EUVD) identifier?
Yes. CVE-2025-48384 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-20677. It is also flagged as exploited in the EUVD (since 2025-08-25).
When was CVE-2025-48384 published?
CVE-2025-48384 was published on 2025-07-08 and last updated on 2026-06-17.

References

Affected products (3)

More vulnerabilities in Git-scm Git

All CVEs affecting Git-scm Git →

Other CWE-59 (Improper Link Resolution Before File Access (Link Following)) vulnerabilities

Browse all CWE-59 (Improper Link Resolution Before File Access (Link Following)) vulnerabilities →