# CVE-2025-48384: Git Link Following

> Attackers can execute arbitrary code via crafted submodule paths and symlinks due to improper config quoting in Git.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 25 Aug 2025 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 8 Jul 2025
- **Updated:** 26 Feb 2026
- **Also known as:** ALPINE-CVE-2025-48384, AZL-65043, AZL-65057, BELL-CVE-2025-48384, BIT-git-2025-48384, CLSA-2025-1752655000, CLSA-2025-1752655315, CLSA-2025-1752655539, CLSA-2025-1752655814, CLSA-2025-1752656083, CLSA-2025-1752683103, CLSA-2025-1752748974, CLSA-2025-1753121050, CLSA-2025-1753207140, CLSA-2025-1754411479, CLSA-2026-1788041847, DEBIAN-CVE-2025-48384, ECHO-5396-ec04-a3b9, GHSA-vwqx-4fm8-6qc9, MINI-3pc6-php8-fx8h, RHSA-2025:11688, RHSA-2025:11793, RHSA-2025:11796, RHSA-2025:11800, RHSA-2025:11801, ROOT-OS-DEBIAN-12-CVE-2025-48384, ROOT-OS-UBUNTU-2004-CVE-2025-48384, UBUNTU-CVE-2025-48384

## What is CVE-2025-48384?

CVE-2025-48384 is a high-severity code injection vulnerability in Apple Xcode, published on 8 Jul 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### 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.

Weakness: CWE-59 (Improper Link Resolution Before File Access), CWE-436 (Interpretation Conflict)

## Which versions are affected by CVE-2025-48384?

1 open source package ship an affected version, including git. It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `git` | Bitnami | All versions | 2.50.1 |
| `git` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:2.18.4-5.el8_2.1 |
| `git-all` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:2.18.4-5.el8_2.1 |
| `git-core` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:2.18.4-5.el8_2.1 |
| `git-core-debuginfo` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:2.18.4-5.el8_2.1 |
| `git-core-doc` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:2.18.4-5.el8_2.1 |
| `git-daemon` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:2.18.4-5.el8_2.1 |
| `git-daemon-debuginfo` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:2.18.4-5.el8_2.1 |
| `git-debuginfo` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:2.18.4-5.el8_2.1 |
| `git-debugsource` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:2.18.4-5.el8_2.1 |
| `git-email` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:2.18.4-5.el8_2.1 |
| `git-gui` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:2.18.4-5.el8_2.1 |
| `git-instaweb` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:2.18.4-5.el8_2.1 |
| `git-subtree` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:2.18.4-5.el8_2.1 |
| `git-svn` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:2.18.4-5.el8_2.1 |
| `git-svn-debuginfo` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:2.18.4-5.el8_2.1 |
| `gitk` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:2.18.4-5.el8_2.1 |
| `gitweb` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:2.18.4-5.el8_2.1 |
| `perl-Git` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:2.18.4-5.el8_2.1 |
| `perl-Git-SVN` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:2.18.4-5.el8_2.1 |
| `git` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:2.27.0-5.el8_4.1 |
| `git-all` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:2.27.0-5.el8_4.1 |
| `git-core` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:2.27.0-5.el8_4.1 |
| `git-core-debuginfo` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:2.27.0-5.el8_4.1 |
| `git-core-doc` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:2.27.0-5.el8_4.1 |
| `git-credential-libsecret` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:2.27.0-5.el8_4.1 |
| `git-credential-libsecret-debuginfo` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:2.27.0-5.el8_4.1 |
| `git-daemon` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:2.27.0-5.el8_4.1 |
| `git-daemon-debuginfo` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:2.27.0-5.el8_4.1 |
| `git-debuginfo` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:2.27.0-5.el8_4.1 |
| `git-debugsource` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:2.27.0-5.el8_4.1 |
| `git-email` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:2.27.0-5.el8_4.1 |
| `git-gui` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:2.27.0-5.el8_4.1 |
| `git-instaweb` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:2.27.0-5.el8_4.1 |
| `git-subtree` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:2.27.0-5.el8_4.1 |
| `git-svn` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:2.27.0-5.el8_4.1 |
| `gitk` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:2.27.0-5.el8_4.1 |
| `gitweb` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:2.27.0-5.el8_4.1 |
| `perl-Git` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:2.27.0-5.el8_4.1 |
| `perl-Git-SVN` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:2.27.0-5.el8_4.1 |

Products: Apple Xcode, Debian Debian Linux, Git-Scm Git.

## How do I fix CVE-2025-48384?

Upgrade git to 2.50.1 or later. US federal agencies must fix it by 15 Sep 2025.

## Is CVE-2025-48384 being exploited?

Yes. Attackers have exploited CVE-2025-48384 in the wild since at least 25 Aug 2025.

Public exploit code:

- Breaking git with a carriage return and cloning RCE (github_poc): https://github.com/acheong08/CVE-2025-48384
- PoC for CVE-2025-48384 (github_poc): https://github.com/liamg/CVE-2025-48384
- PoC dockerfile image for CVE-2025-48384 (github_poc): https://github.com/vinieger/vinieger-CVE-2025-48384-Dockerfile
- CVE-2025-48384 PoC (github_poc): https://github.com/IK-20211125/CVE-2025-48384
- https://github.com/beishanxueyuan/CVE-2025-48384-test (github_poc): https://github.com/beishanxueyuan/CVE-2025-48384-test
- https://github.com/zr0n/CVE-2025-48384-sub (github_poc): https://github.com/zr0n/CVE-2025-48384-sub

## Other vulnerabilities in Apple Xcode

- [CVE-2014-9390](https://insights.sbomify.com/CVE-2014-9390/): JGit Improper Input Validation vulnerability (critical 9.8)
- [CVE-2019-14379](https://insights.sbomify.com/CVE-2019-14379/): Deserialization of untrusted data in FasterXML jackson-databind (critical 9.8)
- [CVE-2018-4164](https://insights.sbomify.com/CVE-2018-4164/): An issue was discovered in certain Apple products. (critical 9.8)
- [CVE-2016-0746](https://insights.sbomify.com/CVE-2016-0746/): Use after free in n/a (critical 9.8)
- [CVE-2004-2687](https://insights.sbomify.com/CVE-2004-2687/): Missing authorization in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-48384 and fix it if it is affected.

What it is: CVE-2025-48384 is a high-severity code injection vulnerability in Apple Xcode, published on 8 Jul 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2025-48384 in the wild since at least 25 Aug 2025.

Affected packages and fixed versions:
- git (Bitnami): affected all versions; fixed in 2.50.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-48384/ (Markdown: https://insights.sbomify.com/CVE-2025-48384/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-48384
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-48384
- OSV: https://osv.dev/vulnerability/CVE-2025-48384

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-48384/
Summaries are generated and may contain mistakes; the official description above is the record.