CVE-2025-48384: Git Link Following Vulnerability

Vulnerability summary

CVE-2025-48384 is a high (CVSS 8.1) Link Following vulnerability in Git. It is known to be exploited: CISA lists it, first on 25-08-2025. EPSS estimates a 4.38% chance of exploitation in the next 30 days, higher than 91.1% of scored vulnerabilities.

Timeline

1. 08-07-2025
   PublishedVulnerability first disclosed.
2. 25-08-2025
   Added to CISA KEVGit Link Following Vulnerability
3. 15-09-2025
   CISA remediation dueApply mitigations per vendor instructions.
4. 26-02-2026
   Last modifiedVulnerability information updated.

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.

• CWE-59Improper Link Resolution Before File Access ('Link Following')The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.
• CWE-436Interpretation ConflictProduct A handles inputs or steps differently than Product B, which causes A to perform incorrect actions based on its perception of B's state.