CVE-2025-48384: Git Link Following
Git · listed in the CISA catalog of actively exploited vulnerabilities since 2025-08-25.
- CVSS v3.1 (CVE record)
- 8.0
- high
- EPSS (exploit probability, 30 days)
- 4.5%
- higher than 91.6% of all CVEs
- Added to CISA KEV
- 2025-08-25
- US federal due date 2025-09-15
- Ubuntu priority
- high
CVE-2025-48384 explained
CVE-2025-48384 is a flaw in how Git handles a trailing carriage return (CR) in config values. Git writes such values unquoted, so the CR is lost on read and a submodule can be checked out to the wrong location. Combined with a symlink to the submodule hooks directory, an executable post-checkout hook may run unintentionally. CISA lists it as known exploited.
Impact
An attacker can cause script execution on the system of a user who works with a crafted repository, which affects confidentiality, integrity and availability. Per the CVSS vector, the attack is network-based with high complexity. It requires low privileges and user interaction. The scope is changed, so the impact can extend beyond Git itself. Execution depends on a submodule path with a trailing CR, a symlink to the hooks directory, and an executable post-checkout hook.
Who is affected
The git source package is affected on all listed releases, and every listed release has a fixed version. Debian 12 (bookworm) is fixed in 1:2.39.5-0+deb12u3. Debian 13 (trixie) is fixed in 1:2.47.3-0+deb13u1. Debian 14 (forky), the testing distribution, is fixed in 1:2.50.1-0.1. Ubuntu 22.04 LTS is fixed in 1:2.34.1-1ubuntu1.13 and Ubuntu 24.04 LTS in 1:2.43.0-1ubuntu7.3. For Ubuntu 16.04 LTS (1:2.7.4-0ubuntu1.10+esm9), 18.04 LTS (1:2.17.1-1ubuntu0.18+esm2) and 20.04 LTS (1:2.25.1-1ubuntu3.14+esm1), fixes are available only through Ubuntu Pro (ESM).
Written with AI from the data on this page and checked against it automatically.
Official 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.
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.
CISA notes
- This vulnerability affects a common open-source component, third-party library, or a protocol used by different products. For more information, please see: github.com/git/git/security/advisories/GHSA-vwqx-4fm8-6qc9
- access.redhat.com/errata/RHSA-2025:13933
- alas.aws.amazon.com/AL2/ALAS2-2025-2941.html
- linux.oracle.com/errata/ELSA-2025-11534.html
- msrc.microsoft.com/update-guide/vulnerability/CVE-2025-48384
- nvd.nist.gov/vuln/detail/CVE-2025-48384
Upstream versions (CVE record)
From the CVE record published by the vendor or CVE numbering authority.
- gitAffectedFixed in
- < 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
- 2.49.0-rc0
- < 2.49.1
- 2.50.0-rc0
- < 2.50.1
not stated
| Product | Affected | Fixed in |
|---|---|---|
| git |
| not stated |
Ubuntu and Debian releases
A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.
Ubuntu 24.04 LTS·git
Fixed: 1:2.43.0-1ubuntu7.3
Ubuntu 22.04 LTS·git
Fixed: 1:2.34.1-1ubuntu1.13
Ubuntu 20.04 LTS·git
fix via Ubuntu Pro
Fixed: 1:2.25.1-1ubuntu3.14+esm1
Ubuntu 18.04 LTS·git
fix via Ubuntu Pro
Fixed: 1:2.17.1-1ubuntu0.18+esm2
Ubuntu 16.04 LTS·git
fix via Ubuntu Pro
Fixed: 1:2.7.4-0ubuntu1.10+esm9
testing distribution
Fixed: 1:2.50.1-0.1
Fixed: 1:2.47.3-0+deb13u1
Fixed: 1:2.39.5-0+deb12u3
What to do
- Update the
gitpackage to the fixed version for your release from the distribution archive. - On Ubuntu 16.04, 18.04 and 20.04 LTS, enable Ubuntu Pro (ESM) to receive the fixed
gitpackage. - Plan upgrades of Ubuntu 16.04 LTS systems to a supported release, because that release is end of life.
- Verify the installed
gitversion on developer workstations, build servers and CI runners. - Prioritize remediation, since the flaw is in the CISA Known Exploited Vulnerabilities catalog.
Written with AI from the data on this page and checked against it automatically.
Check and fix on a server
Run on each Ubuntu or Debian server. Replace git with the source package from the table above.
1. Show installed packages built from the source package, with their versions
dpkg-query -W -f='${binary:Package} ${Version} ${source:Package}\n' | awk '$3=="git"'2. Compare each installed version with the fixed version for your release from the table
I=INSTALLED_VERSION; F=FIXED_VERSION # replace both
dpkg --compare-versions "$I" lt "$F"; case $? in 0) echo vulnerable ;; 1) echo "fixed or newer" ;; *) echo "check the versions" ;; esac3. Install the fix
sudo apt update && sudo apt install --only-upgrade $(dpkg-query -W -f='${binary:Package} ${source:Package}\n' | awk '$2=="git"{print $1}')Services keep running the old code until they are restarted – restart the affected service or check with needrestart.
Rows marked “fix via Ubuntu Pro”: these fixes are only installable with an Ubuntu Pro subscription (ESM). Attach the machine first (sudo pro attach, then sudo pro enable esm-infra esm-apps), then run the commands above.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-436 Interpretation Conflict, CWE-59 Improper Link Resolution Before File Access ('Link Following')
Questions about CVE-2025-48384
- Is CVE-2025-48384 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-08-25, with a US federal due date of 2025-09-15. Whether it has been used in ransomware campaigns is listed as unknown.
- Which upstream Git versions fix this?
- Upstream lists fixes 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. Distribution packages carry their own fixed versions, such as
1:2.43.0-1ubuntu7.3on Ubuntu 24.04 LTS. - Do I need Ubuntu Pro to get the fix?
- Only on Ubuntu 16.04, 18.04 and 20.04 LTS, where the fix is published through Ubuntu Pro (ESM). Ubuntu 22.04 and 24.04 LTS receive the fix from the standard archive.
Written with AI from the data on this page and checked against it automatically.
References
Other advisories
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.