Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 Bitnami
CISA KEV · ACTIVELY EXPLOITED

Git allows arbitrary code execution through broken config quotingGHSA-vwqx-4fm8-6qc9

GHSA-vwqx-4fm8-6qc9 is a 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.

Also known asCVE-2025-48384
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
2 known
Exploitation data as of Oct 24, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

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 GHSA-vwqx-4fm8-6qc9.

EPSS Exploitation Probability

via FIRST.org ↗
4.4%probability of exploitation in next 30 days
Lower Risk+0.18%
Lower risk than most CVEs91th percentile — riskier than 91% of all scored CVEsHighest risk
0.00%1.85%3.70%5.55%0.5%4.4%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected
📦git

Real-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

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦Bitnamigitall versions2.50.1

Affected Products

3 products · 10 configurations
Application
xcodeapple
< 26.0
range
OS
debian linuxdebian
1 version
11.0
Application
gitgit-scm
≥ 2.50.0 && < 2.50.1
range
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

acheong08/CVE-2025-48384

Breaking git with a carriage return and cloning RCE

⭐ 53🍴 28Jul 2026

liamg/CVE-2025-48384

PoC for CVE-2025-48384

⭐ 20🍴 20Jul 2026

Detection & mitigation playbook

Open-source dependency

  1. Detect

    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.

  2. Fix

    Update git to 2.50.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vwqx-4fm8-6qc9 is resolved across your whole dependency graph.

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

Red HatImportant

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…

Workaround published by Red Hat
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 GHSA-vwqx-4fm8-6qc9 (CC BY 4.0)
ProductFixed inAdvisory
Red Hat Enterprise Linux 10git-0:2.47.3-1.el10_0RHSA-2025:11533
Red Hat Enterprise Linux 7 Extended Lifecycle Supportgit-0:1.8.3.1-25.el7_9.1RHSA-2025:11688
Red Hat Enterprise Linux 8git-0:2.43.7-1.el8_10RHSA-2025:11534
Red Hat Enterprise Linux 8.2 Advanced Update Supportgit-0:2.18.4-5.el8_2.1RHSA-2025:11793
Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Supportgit-0:2.27.0-5.el8_4.1RHSA-2025:11800
Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Supportgit-0:2.31.8-3.el8_6.1RHSA-2025:11801
Red Hat Enterprise Linux 8.8 Telecommunications Update Servicegit-0:2.39.5-1.el8_8.2RHSA-2025:11794
Red Hat Enterprise Linux 9git-0:2.47.3-1.el9_6RHSA-2025:11462
UbuntuHIGH
USN-7626-1Ubuntu

Frequently Asked Questions

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 alter
O3 Security · Impact-Aware SCA

Is GHSA-vwqx-4fm8-6qc9 in your dependencies?

Find it across Bitnami, including transitive dependencies.

Scan my dependencies How O3 SCA works
Git allows arbitrary code execution through broken config…