What is CVE-2025-48384?

CVE-2025-48384 is Git allows arbitrary code execution through broken config quoting. The supplied enrichment data classifies it as Path Traversal mapped to CWE-436 CWE-436; CWE-59 Link Following.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Is there a public exploit?

75 public PoC repositories reported; 1 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2025-48384 using CVSS 8, EPSS 4%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

Publicly linked actor or ransomware signals in the supplied enrichment data: Void Rabisu (), RomCom (), HAZY TIGER (), Gamaredon Group (), APT3 (). Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVhighPath Traversalpublic exploit

CVE-2025-48384

CVE-2025-48384 — Git allows arbitrary code execution through broken config quoting

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2025-48384 in CISA KEV with required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

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.

Published Jul 8, 2025Updated Jun 17, 2026Sources: NVD, git (CNA), CISA, FIRST EPSS, Microsoft MSRC, Red Hat (VEX), SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Aug 25, 2025

EPSS

ahead of 90% of scored CVEs

Affects

git

14 products listed

CVSS base

high · 2 sources

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade git to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

CISA required action

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Federal deadline Sep 15, 2025 — passed 360 days ago

Red Hat VEX · CVE-2025-48384

fixed587affected13not affected655

vendor_fix: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

vendor_fix: For OpenShift Container Platform 4.12 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster an…

vendor_fix: The RHEL-8 based Middleware Containers container images provided by this update can be downloaded from the Red Hat Container Registry at registry.access.redhat.com. Installation i…

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
git	git	< 2.43.7	Vulnerable
git	git	>= 2.44.0-rc0, < 2.44.4	Vulnerable
git	git	>= 2.45.0-rc0, < 2.45.4	Vulnerable
git	git	>= 2.46.0-rc0, < 2.46.4	Vulnerable
git	git	>= 2.47.0-rc0, < 2.47.3	Vulnerable
git	git	>= 2.48.0-rc0, < 2.48.2	Vulnerable
git	git	>= 2.49.0-rc0, < 2.49.1	Vulnerable
git	git	>= 2.50.0-rc0, < 2.50.1	Vulnerable
Microsoft	Microsoft Visual Studio 2022 version 17.8	—	Vulnerable
Microsoft	Microsoft Visual Studio 2022 version 17.10	—	Vulnerable
Microsoft	Microsoft Visual Studio 2022 version 17.12	—	Vulnerable
Microsoft	Microsoft Visual Studio 2022 version 17.14	—	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Changed

Attack Complexity

High

Attack Vector

Network

Privileges Req

Low

User Interaction

Required

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
8	CVSS 3.1	high	1.3	6	GitHub (CNA), Red Hat (VEX)
8.1	CVSS 3.1	high	—	—	git (CNA)

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-436 · Interpretation Conflict

Unexpected State
Varies by Context::

CWE-59 · Improper Link Resolution Before File Access ('Link Following')

Read Files or Directories
Modify Files or Directories
Bypass Protection Mechanism
Execute Unauthorized Code or Commands

Mitigation: Follow the principle of least privilege when assigning access rights to entities in a software system. Denying access to a file can prevent an attacker from replacing that file with a link to a sensitive file. Ensure good compartmentalization in the system to provide protected areas that can be trusted.::

Weakness & attack patterns

CWE-436
CWE-59Link Following

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-132 · Symlink AttackCAPEC-17 · Using Malicious FilesCAPEC-76 · Manipulating Web Input to File System CallsCAPEC-35 · Leverage Executable Code in Non-Executable Files

T1547.009Boot or Logon Autostart Execution: Shortcut Modification
T1574.005Hijack Execution Flow: Executable Installer File Permissions Weakness
T1574.010Hijack Execution Flow: Services File Permissions Weakness

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Aug 25, 2025

Federal deadline

Sep 15, 2025

passed 360 days ago

Ransomware use

Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

1 of the 5 sampled are weaponized

Exploit entries

Exploit-DB and CTI exploit indexes

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

8 more posts on this CVEShowing 5 of 13 · Who is discussing this CVE, and how loudlyUnlock free

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable git, Microsoft Visual Studio 2022 version 17.8, Microsoft Visual Studio 2022 version 17.10, Microsoft Visual Studio 2022 version 17.12, Microsoft Visual Studio 2022 version 17.14, Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10), Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8).
Monitor for scanner or exploit-pattern traffic after 75 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPS

Groups associated with this CVE

Groups reported in connection with this vulnerability. A reported association, not a confirmed observation of that group using it — and not scoped to any sector or campaign.

Void RabisuRomComHAZY TIGERGamaredon GroupAPT3

11 more threat groups on this CVEShowing 5 of 16 · Attribution, campaigns and the malware each one runsUnlock free

ip43.153.76.2458
Abuse.ch-ThreatFox-C&Cs · Apr 15, 2026
hostnamehunting-decoy.com39
SOCRadar Attack Surface Intelligence(ASI) · Jul 11, 2026
hash47ecaab5cd6b26fe18d9759a9392bce81ba379817c53a3a468fe9060a076f8ca94
INQUEST LAB · Apr 29, 2024

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Cve is exploited Fomovet/cve-2025-48384
Jul 1, 2026 · SOCRadar CTI
Added · CVSS 3.1 8.0 (AV:N)
Jun 17, 2026 · NVD
Cve is exploited DayDayDayDreaming/backup-exec-cve-48384
Mar 22, 2026 · SOCRadar CTI
2025
Cve is exploited zr0n/CVE-2025-48384-main
Dec 5, 2025 · SOCRadar CTI
Added to CISA KEV catalog
Aug 25, 2025 · CISA
Initial · CVE published
Jul 8, 2025 · NVD

Source activity

Readings a source repeats on a schedule, counted rather than listed.

17×SVRS was changedNov 12, 2025 – Jul 17, 2026 · SOCRadar CTI
8×Github ReposDec 4, 2025 – Jun 21, 2026 · SOCRadar CTI
1×CVE modified by NIST: CWE updated.Feb 27, 2026 · SOCRadar CTI

References

28 on the record

github.com/git/git/security/advisories/GHSA-vwqx-4fm8-6qc9
Vendor Advisory, NIST, Mitre
seclists.org/fulldisclosure/2025/Sep/60
Mailing List, Third Party Advisory, NIST
www.openwall.com/lists/oss-security/2025/07/08/4
Mailing List, NIST
lists.debian.org/debian-lts-announce/2025/10/msg00003.html
Mailing List, Third Party Advisory, NIST
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-48384
US Government Resource
my.visualstudio.com/Downloads?q=Visual Studio 2022 version 17.8
Vendor Advisory
learn.microsoft.com/en-us/visualstudio/releases/2022/release-notes
Vendor Advisory
my.visualstudio.com/Downloads?q=Visual Studio 2022 version 17.10
Vendor Advisory

Coverage

10 stories from the feeds we poll

5 more reports on this CVEShowing 5 of 10 · Vendor research and security press coverageUnlock free

Elsewhere on this site

gitevery CVE for this vendor
Microsoftevery CVE for this vendor
August 2025what else CISA listed
Path Traversalsame class
CWE-436other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

Only the 3 indicator(s) reported for this CVE are available; no packet-level or host-forensic artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2025-48384 is Git allows arbitrary code execution through broken config quoting, a high vulnerability affecting git, Microsoft Visual Studio 2022 version 17.8, Microsoft Visual Studio 2022 version 17.10, Microsoft Visual Studio 2022 version 17.12, Microsoft Visual Studio 2022 version 17.14, Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10), Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8) from git, Microsoft. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 75 public PoC repositories reported; 1 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 8 describes technical severity, while EPSS 4% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.