Git Carriage Return Flaw Enables Code Execution During Submodule Initialization
A high-severity vulnerability tracked as CVE-2025-48384 affects Git’s handling of configuration values containing trailing carriage returns, creating a path for unintended script execution during submodule initialization. According to Armis, the flaw can be abused when an attacker can influence the relevant configuration context, potentially turning routine clone or submodule operations into code execution. Microsoft’s Security Update Guide also lists the issue, identifying it as a Git/GitHub vulnerability.
Public exploit activity quickly followed disclosure, with multiple GitHub repositories publishing proof-of-concept material for CVE-2025-48384, including variants described as working over HTTPS and others explicitly labeling the issue as carriage-return-driven remote code execution on cloning. The appearance of several PoC repositories indicates that exploit details are broadly accessible, increasing the likelihood of weaponization against developers and build environments that process untrusted repositories or submodules.

Get ahead of threats like this
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
How this story unfolded
2 events from the most recent confirmed update back to the earliest known activity.
Public proof-of-concept exploit for CVE-2025-48384 appears on GitHub
A GitHub repository publishing a proof-of-concept for CVE-2025-48384 was made public. The PoC indicated that exploit details had become publicly available shortly after disclosure.
CVE-2025-48384 disclosed as a Git carriage-return handling flaw
A vulnerability identified as CVE-2025-48384 was disclosed in Git. The flaw involves improper handling of trailing carriage returns in configuration values, which can trigger unintended script execution during submodule initialization if an attacker can influence the configuration context.
Related entities
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
Sources
10 references tracked. Mallory keeps watching after this page renders.
GitHub - vignesh21-git/CVE-2025-48384: GIT vulnerability | Carriage Return and RCE on cloning · GitHub
github.com
Open sourceGitHub - s41r4j/CVE-2025-48384: GIT vulnerability | Carriage Return and RCE on cloning · GitHub
github.com
Open sourceGitHub - jacobholtz/CVE-2025-48384-poc: PoC for CVE-2025-48384 · GitHub
github.com
Open sourceGitHub - arun1033/CVE-2025-48384 · GitHub
github.com
Open sourceGitHub - IK-20211125/CVE-2025-48384: CVE-2025-48384 PoC · GitHub
github.com
Open sourceGitHub - vinieger/CVE-2025-48384: PoC for CVE-2025-48384 - but with HTTPS instead · GitHub
github.com
Open sourceCVE-2025-48384 | High Severity | Armis
cve.armis.com
Open sourceCVE-2025-48384 - Security Update Guide - Microsoft - GitHub: CVE-2025-48384 Git Symlink Vulnerability
msrc.microsoft.com
Open sourceSee the full picture, correlated to your attack surface.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.


