Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-48384Git allows arbitrary code execution through broken config quoting

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.

Exploited in the wild

CISA lists this vulnerability in its Known Exploited Vulnerabilities catalog as Git Link Following Vulnerability.

Added
25 Aug 2025
Fix due (US federal)
15 Sept 2025
Used by ransomware
Not known

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

ENISA's EU Vulnerability Database lists it as exploited, from CISA's KEV, since 25 Aug 2025.

Public exploit

An exploit or proof of concept is public: anyone can try it against an unpatched system. CISA's SSVC rates its exploitation: it is being exploited.

Timeline

  1. ID reserved

    By GitHub_M

  2. · 50 days later

    Published

  3. · 48 days later

    Added to CISA KEV

    Known exploited in the wild

  4. · 6 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-48384, by who scored it
Scored byCVSSScoreVector
GitHub_MCNA (assigner)3.1High8.1CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H
NVDNVD · Analyzed3.1High8.0CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H
EPSS (exploitation in 30 days)
4.5% · top 8.4% of all CVEs (13 Nov 2026)
CISA SSVC
Exploitation: active · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.1.

Affected products

  • git · git

    • 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

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-48384 badge
[![CVE-2025-48384](https://cveledger.app/badge/CVE-2025-48384.svg)](https://cveledger.app/cve/CVE-2025-48384)

Record last updated .