← gociux.comall exploited CVEs

Exploited vulnerability · CISA KEV

Is CVE-2025-48384 exploited? Yes: in CISA KEV since 25 Aug 2025

Gociux · Git · data: CISA KEV, CVE record, FIRST EPSS

Yes. CVE-2025-48384, Git Link Following Vulnerability, is being exploited in the wild. CISA added it to its Known Exploited Vulnerabilities catalog on 25 Aug 2025, 48 days after it was published. It affects Git. If you run it, CISA's required action is: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

exploitedYesCISA KEV · 25 Aug 2025
ransomwareNot knownno confirmed use
EPSStop 10%more likely than most to be exploited
severity8.1CVSS 3.1 · high
US federal due15 Sep 2025BOD 22-01 deadline

What it is

Git contains a link following vulnerability that stems from Git’s inconsistent handling of carriage return characters in configuration files.

VendorGit (1 exploited CVE in KEV)
ProductGit
VulnerabilityGit Link Following Vulnerability
WeaknessCWE-59, CWE-436
Published8 Jul 2025
Added to KEV25 Aug 2025
Reported by (CNA)GitHub_M

What to do

  1. Check whether you run it. Look for Git in your asset inventory, including appliances and cloud images. Stack check lists every exploited Git CVE at once.
  2. Apply the fix. Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
  3. If you can't patch today, take the affected service off the internet or restrict who can reach it, and check its logs for signs of compromise since 8 Jul 2025.
  4. Get told next time. Email alerts when CISA adds a CVE for Git.

References

Questions

Is CVE-2025-48384 being exploited?

Yes. CISA added CVE-2025-48384 to the Known Exploited Vulnerabilities catalog on 25 Aug 2025, which means there is reliable evidence of exploitation in the wild.

Is CVE-2025-48384 used in ransomware attacks?

CISA does not list known ransomware use for it. That can change, and exploitation alone is reason to fix it first.

How do I fix CVE-2025-48384?

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Check Git's advisory for the fixed versions, and if you can't patch quickly, restrict access to the affected Git and watch it for signs of compromise.

Sources: CISA KEV (exploitation, ransomware use, required action, due date), the CVE record (publication date, CVSS, CNA), NVD and FIRST EPSS (live score). More: all KEV additions in August 2025 · act-now radar.

Running Git in a regulated environment?

We check exposure across your estate, patch or mitigate with your team, and set up detection for what attackers do after exploiting it.

Get in touch →