CVE-2025-48384
Git-Scm Git ≤ 2.43.7
Raw vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:HSummary
CVE-2025-48384 is a high-severity Link Following (CWE-59) vulnerability in Git-Scm Git. Its CVSS base score is 8.0 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Path Interception (T1034); ranked in the top 15% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SA-11 (Developer Testing and Evaluation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
Git is affected by a configuration parsing inconsistency that occurs when submodule paths contain a trailing carriage return. The vulnerability stems from Git stripping CRLF characters on config reads while failing to quote trailing CR characters on writes, which causes an altered path to be used during submodule checkout. This can result in the submodule being placed at an unexpected location if a symlink redirects the mangled path to the hooks directory, allowing an executable post-checkout hook to run.
An attacker who can supply or influence a malicious .gitmodules file or repository configuration can exploit the flaw to achieve arbitrary code execution on a victim's system during submodule initialization. The attack requires the victim to perform a submodule update against attacker-controlled content and succeeds when a symlink and executable hook are present at the altered path, yielding high-impact outcomes under the reported CVSS vector.
The referenced Git security advisory and distribution lists state that the issue is resolved in versions 2.43.7, 2.44.4, 2.45.4, 2.46.4, 2.47.3, 2.48.2, 2.49.1, and 2.50.1; users should upgrade and avoid initializing submodules from untrusted sources until patched. The CVE appears in the CISA known exploited vulnerabilities catalog, indicating confirmed in-the-wild exploitation, while the current EPSS score of 0.0060 remains low.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-20677
Vulnerability Data
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).…
more
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(s)
- KEV Date Added
- 25 August 2025
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V15.4.2
Mitigating Controls (NIST 800-53 r5) AI
Proper enforcement of access authorizations on the resolved target resource stops a link from reaching an unintended object.
Developer testing and evaluation can discover cases where two products interpret the same inputs or state transitions differently.
Strict, consistently applied input validation reduces the chance that one product will accept data the other product rejects or interprets differently.
Least-privilege limits the damage an attacker can cause after following an unintended link.
Applying security engineering principles during design can require unambiguous protocol and data-format specifications that eliminate divergent interpretations between products.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require code to validate paths and avoid unsafe link following.
Correlating logs from multiple products can surface discrepancies caused by interpretation conflicts.
Runtime monitoring of software behavior can detect adverse outcomes stemming from differing interpretations.
Supplier risk assessments can identify products whose differing interpretations create systemic exposure.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect link-following flaws before release.
Secure SDLC practices can mandate link-resolution checks and canonicalization before file access.
Application security requirements can explicitly require safe handling of symbolic links and path traversal.
Secure architecture principles include input validation and safe file-access design patterns.
Secure coding standards directly address canonicalization and symlink attacks during implementation.
Access-control rules can limit which files are reachable, reducing exposure to malicious links.