IRONSMITHINTEL
HIGHCVSS8.0
|
Actively Exploited
|CISA KEV|CVE-2025-48384|Auth: low — authenticated user|Reboot: required|Manual only

Git Link Following Vulnerability

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

Published Jul 8, 2025 · Updated May 16, 2026
Why patchRisk explained in plain English
Worst-case scenarioIf unpatched

A remote attacker, with a low-privilege account, can achieve full data confidentiality loss, arbitrary modification of data, complete denial of service or system unavailability. Federal agencies are required to remediate by 2025-09-15 under CISA BOD 22-01.

How the attack worksNo clicks needed

This is a Software Vulnerability (CWE-59) (CWE-59) vulnerability in Git Git. 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. Exploitation requires remote network access, higher attack complexity, a low-privilege authenticated account, and user interaction required.

Am I affected?Quick check

Probably yes if any of these apply:

IT Security
Running git: v < 2.43.7, 2.44.0 ≤ v < 2.44.4, 2.45.0 ≤ v < 2.45.4, 2.46.0 ≤ v < 2.46.4, 2.47.0 ≤ v < 2.47.3, 2.48.0 ≤ v < 2.48.2, 2.49.0 ≤ v < 2.49.1, 2.50.0 ≤ v < 2.50.1; debian linux: 11.0; xcode: v < 26.0
Real-world incidentsWhat we've seen

CISA added this CVE to the Known Exploited Vulnerabilities catalog on 2025-08-25 based on evidence of active exploitation in the wild. Federal agencies required to remediate by 2025-09-15.

How to patch

Manual remediation steps

Apply the Vendor Patch

This vulnerability is in the CISA Known Exploited Vulnerabilities catalog — apply the vendor's security update as soon as possible.

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.

References

    1
    Vendor advisory: https://access.redhat.com/errata/RHSA-2025:13933
    1
    NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2025-48384
    1
    CISA KEV: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-48384
PowerShell automationComing soon

No tested PowerShell script for this entry yet. We’re prioritising automation based on user demand.