Home › Intelligence › Brief
VULNERABILITY BRIEF🟠 High Vulnerability

Git Link‑Following Vulnerability (CVE‑2025‑48384) Risks Malicious Configuration Exploits

CISA’s KEV list flags CVE‑2025‑48384, a high‑severity flaw where Git improperly processes carriage‑return characters in its configuration files, enabling malicious link execution. The issue affects all unpatched Git installations and can compromise CI/CD pipelines, making secure configuration controls a priority for audit‑ready organizations.

LiveThreat™ Intelligence · 📅 October 07, 2026· 📰 nvd.nist.gov
🟠
Severity
High
VU
Type
Vulnerability
🎯
Confidence
High
🏢
Affected
2 sector(s)
✅
Actions
4 recommended
📰
Source
nvd.nist.gov

Git Link‑Following Vulnerability (CVE‑2025‑48384) Risks Malicious Configuration Exploits

What It Is — Git 2025‑48384 is a link‑following flaw caused by inconsistent handling of carriage‑return (\r) characters in Git’s configuration files. An attacker who can inject a crafted line into a repo’s config can cause Git to follow a malicious URL, potentially leading to arbitrary command execution on the host processing the config.

Exploitability — No public exploit has been released, but the vulnerability scores 7.5 (CVSS v3.1 – High) and can be weaponized in automated CI/CD pipelines that automatically pull and apply configuration files.

Affected Products — All Git installations (client and server) that read configuration files prior to the vendor‑released patch (versions 2.40 and earlier).

Why It Matters for Trust & Control Assurance

  • Demonstrates the need for secure configuration management controls that verify the integrity of critical tooling files.
  • Continuous evidence of configuration‑file hygiene supports audit readiness and a defensible control‑assurance posture.
  • Enterprises that must prove “secure development” to regulators or partners will be asked to show that such low‑level tool vulnerabilities are mitigated and monitored.

Recommended Actions

  • Apply the Git security patch released on 2025‑09‑15 (or later).
  • Audit all existing Git configuration files for stray \r characters or unexpected link entries.
  • Implement automated integrity checks (hash‑based or signed configs) as part of your CI/CD pipeline.
  • Log and monitor any Git configuration changes; retain evidence for compliance reviews.

Source: CISA KEV – CVE‑2025‑48384

📰 Original Source
https://nvd.nist.gov/vuln/detail/CVE-2025-48384 ↗

This LiveThreat Intelligence Brief is an independent analysis. Read the original reporting at the link above.

From the Verisq platform · Trust Operations

Misconfigurations are control gaps in disguise.

Verisq AI Trust Operations turns findings like this into mapped controls with continuous evidence, keeping your audit readiness current instead of point-in-time.

Map your controls with Verisq AI Trust Operations →