CVE-2025-48384: high-severity vulnerability in git
Git allows arbitrary code execution through broken config quoting
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
Prioritize patching. It under exploitation confirmed by CISA and has a public proof of concept.
Official vendor statements in CSAF/VEX format: whether their product is affected, already fixed, or ruled out — and why. These are the vendor's assertions, not Vexday's judgment.
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Git fails to properly quote config values with trailing carriage returns, causing submodules to be checked out to wrong locations. If a symlink redirects to Git hooks, an attacker could trick Git into executing malicious scripts during submodule setup.
When Git reads config values, it strips CRLF characters, but fails to quote values containing trailing CR on write, causing path misinterpretation during submodule initialization. An attacker can craft a repository with a submodule path containing trailing CR that, combined with a symlink pointing to the hooks directory, triggers unintended execution of post-checkout hooks. Requires user to clone a malicious repository or update submodules (CWE-436: Interpretation Conflict, CWE-59: Improper Link Resolution).
The full analysis of this CVE is available in Portuguese →
In the same product, most dangerous first.