VulnTideExploited vulnerabilities, by vendor. Data as of .
Known exploitedIn CISA's KEV catalog since Ransomware use: unknown
Git Git

CVE-2025-48384: Git Link Following Vulnerability

Is it exploited?

Yes. CISA added it to the Known Exploited Vulnerabilities catalog on , 48 days after the CVE record was published.

How likely is exploitation in the next 30 days?
4.4%

EPSS score, percentile 91.3 of all scored records

How severe?
8.1 High

CVSS v3.1 base score, given by the CNA

What should I do?

CISA deadline . Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

The CVE record links no vendor advisory, patch or mitigation.

Which versions are affected?

Affected

  • < 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

and 2 more in the table below

Versions by product

Source: CISA Known Exploited Vulnerabilities (KEV) catalog, 2026.10.28, as of ; FIRST Exploit Prediction Scoring System (EPSS), v2026.06.15, as of ; CVE List V5 (CVE Program), cve_2026-10-28_0000Z, as of . About the data.

What to do

Required action, set by CISA

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 due date for this action: .

Advisories and patches

The CVE record links no vendor advisory, patch or mitigation.

Linked from CISA's catalog entry

Affected products and versions

As listed in the CVE record.

git git
StatusVersions
Affected< 2.43.7
Affected>= 2.44.0-rc0, < 2.44.4
Affected>= 2.45.0-rc0, < 2.45.4
Affected>= 2.46.0-rc0, < 2.46.4
Affected>= 2.47.0-rc0, < 2.47.3
Affected>= 2.48.0-rc0, < 2.48.2
Affected>= 2.49.0-rc0, < 2.49.1
Affected>= 2.50.0-rc0, < 2.50.1

Source: CVE List V5 (CVE Program), cve_2026-10-28_0000Z, as of . About the data.

About this vulnerability

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

Summary: CISA's KEV catalog, as of .

  • CISA added CVE-2025-48384 to its Known Exploited Vulnerabilities (KEV) catalog on 25 Aug 2025.
  • CISA's ransomware flag for this entry is "Unknown": no evidence of ransomware use in the catalog, which is not proof of none.
  • The due date CISA sets for the required action is 15 Sep 2025.
  • The CVE record was published on 8 Jul 2025, 48 days before it was added to KEV.
  • The CVE record carries a CVSS v3.1 base score of 8.1 (High), given by its CNA.
  • FIRST's EPSS model puts the probability of exploitation in the next 30 days at 4.4% (percentile 91.3), as of 28 Oct 2026.
  • CISA's SSVC assessment in the CVE record: exploitation active, automatable no, technical impact total.

Source: CISA Known Exploited Vulnerabilities (KEV) catalog, 2026.10.28, as of ; CVE List V5 (CVE Program), cve_2026-10-28_0000Z, as of ; FIRST Exploit Prediction Scoring System (EPSS), v2026.06.15, as of . About the data.

Description

Git allows arbitrary code execution through broken config quoting

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.

Source: CVE List V5 (CVE Program), cve_2026-10-28_0000Z, as of . About the data.

Weakness

  • CWE-436: Interpretation Conflict
  • CWE-59: Improper Link Resolution Before File Access ('Link Following')

CWE and CAPEC are maintained by MITRE; the entries are those named in the CVE record and the KEV entry.

Timeline

DateEvent
CVE record published
Added to CISA KEV
CISA due date for the required action
CVE record last updated

References