At a glance
Actively exploited in the wild — prioritise confirming exposure.
Medium rather than High: exposure is scored at a default because we cannot see your systems or suppliers. If it touches your systems or suppliers, treat it as High.
Briefing
- Do not treat uncorroborated claims as confirmed breaches.
Questions to ask IT
- Are we affected by CVE-2025-48384, and which of our systems would be?
- Have we checked whether it has already been used against us?
- If it is not yet patched, what mitigation is in place, and will the fix be done by 11 Nov?
Next steps
- Confirm exposure, mitigation status and any service interruption risk.
Vulnerability facts
Full CVE detail CVE-2025-48384- 8.0 · HighExploitable over the network with a low-privilege account, under specific conditions, but only if a user takes an action, such as opening a file or link. High impact on confidentiality, integrity and availability, and it can reach beyond the vulnerable system.CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H
- Listed: attacks using it have been seen (on the catalogue since )
- ~4.4% estimated chance of attack in 30 days
- CVE-2025-48384 has estimated attack likelihood 0.02839 (~2.8% estimated chance of exploitation in 30 days; 85.2th percentile) as of 2026-07-31 — probability signal, not confirmed exploitation
Next steps
- Confirm whether affected products/versions are present and prioritise patching or mitigations
Summary
- Git contains a link following vulnerability that stems from Git’s inconsistent handling of carriage return characters in configuration files.
- CVE-2025-48384 is listed in known-exploited catalogue (exploitation in the wild)
- 8% estimated chance of exploitation in 30 days; 85.
- Authoritative catalogues report active exploitation of this vulnerability.
Why this matters in the UK
- Known-exploited catalogue reports exploitation in the wild
Part of D-Link device vulnerabilities and exploitation
Pulse
Last checked 4d ago · Recheck overdue since 5 Nov 2026, 23:37 UK time · 2 quiet checks collapsed
Suggested changed to 7d.
Listed on the — prioritise confirming exposure and patching.
1 quiet check hidden.
Sources
Git Link Following Vulnerability
How we know
Statements extracted from sources. Higher confidence means stronger corroboration.
- ConfirmedHeadline90% confidence
Git Link Following Vulnerability
- ConfirmedSummary fact75% confidence
Git contains a link following vulnerability that stems from Git’s inconsistent handling of carriage return characters in configuration files. Affects Git Git. Known ransomware campaign use: Unknown. 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.
- ConfirmedCVE identifier95% confidence
Event involves CVE-2025-48384
- ConfirmedKnown-exploited catalogue98% confidence
CVE-2025-48384 is listed in known-exploited catalogue (exploitation in the wild)
- ConfirmedEstimated attack likelihood95% confidence
CVE-2025-48384 has estimated attack likelihood 0.02839 (~2.8% estimated chance of exploitation in 30 days; 85.2th percentile) as of 2026-07-31 — probability signal, not confirmed exploitation