CVE-2025-48384 — git
HIGHCVE-2025-48384 is a high-severity (CVSS 8) CWE-59 vulnerability in git. It is in CISA's Known Exploited Vulnerabilities catalog (added 2025-08-25) — treat it as actively exploited and patch now. A fix is available for git — see the affected versions and patch details below.
Git allows arbitrary code execution through broken config quoting
Exploitation Status
Actively exploited in the wild
- Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2025-08-25. Federal agencies were required to remediate by 2025-09-15.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2025-48384.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2025-48384 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 395,249 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
gitReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Bitnami packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦Bitnami | git | all versions | 2.50.1 |
Affected Products
xcodeappledebian linuxdebiangitgit-scmResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for git, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update git to 2.50.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-48384 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This vulnerability marked as Important and not Moderate flaw because it undermines Git’s path and config integrity by allowing carriage return (\r) injection to manipulate submodule checkout behavior. Git previously failed to quote config values containing trailing CR, causing the value to be misinterpreted when read…
To mitigate this issue, avoid using --recurse-submodules when cloning repositories from untrusted sources; instead, clone normally and only initialize or update submodules manually after reviewing them.Source: Red Hat security advisory for CVE-2025-48384 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Enterprise Linux 10 | git-0:2.47.3-1.el10_0 | RHSA-2025:11533 |
| Red Hat Enterprise Linux 7 Extended Lifecycle Support | git-0:1.8.3.1-25.el7_9.1 | RHSA-2025:11688 |
| Red Hat Enterprise Linux 8 | git-0:2.43.7-1.el8_10 | RHSA-2025:11534 |
| Red Hat Enterprise Linux 8.2 Advanced Update Support | git-0:2.18.4-5.el8_2.1 | RHSA-2025:11793 |
| Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support | git-0:2.27.0-5.el8_4.1 | RHSA-2025:11800 |
| Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support | git-0:2.31.8-3.el8_6.1 | RHSA-2025:11801 |
| Red Hat Enterprise Linux 8.8 Telecommunications Update Service | git-0:2.39.5-1.el8_8.2 | RHSA-2025:11794 |
| Red Hat Enterprise Linux 9 | git-0:2.47.3-1.el9_6 | RHSA-2025:11462 |
Frequently Asked Questions
Is CVE-2025-48384 in your dependencies?
Find it across Bitnami, including transitive dependencies.