Vulnerability

CVE-2025-60710

High· 7.8KEVCVSS7.8EPSS19%

.rules3/5

Microsoft Windows Link Following Vulnerability

Microsoft Windows contains a link following vulnerability that allows for privilege escalation

Threat signal

91/100

Severe

Severity

high

CVSS

7.8

EPSS

19%

Active

KEV

CISA KEV — actively exploited

47d overdue

AffectedMicrosoft — Windows

Added to KEV

2026-04-13

Federal patch due (BOD 22-01)

2026-04-27

Required action (CISA verbatim)

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

Vendor advisory + references

CISA description: “Microsoft Windows contains a link following vulnerability that allows for privilege escalation”

CVSS

v3.1Open in FIRST calculator →

7.8/ 10HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack VectorLocalRequires local access — shell, console, or local app.
Attack ComplexityLowNo special conditions — exploit works reliably.
Privileges RequiredLowStandard user privileges sufficient.
User InteractionNoneFully automated — no victim action needed.
ScopeUnchangedImpact contained to the vulnerable component.
Confidentiality ImpactHighTotal disclosure of sensitive data.
Integrity ImpactHighTotal compromise of integrity — full data modification possible.
Availability ImpactHighTotal loss of availability — full DoS possible.

EPSS

Exploit prediction · 30-day horizonFIRST.org →

19.0%

probability of exploitation in next 30 days

p95

higher than 95% of all CVEs

3-day trend↑ 0pp

Above the FIRST 'patch on a priority schedule' threshold.

Vendor VEX

No VEX statements published for CVE-2025-60710. Vendors publish VEX (Vulnerability Exploitability eXchange) to assert per-product whether a CVE is actually exploitable in their distribution.

SSVCAct

Active exploitation with total impact on essential/support systems

exploitation: active
automatable: no
impact: total
mission: support

Lifecycle

2026-04-13Added to CISA KEVransomware: Unknown
2026-04-13Published
2026-04-27Federal patch due (BOD 22-01)
2026-06-12Last modified1 source

No source-event history recorded yet. New revisions will appear here as ingestors re-fetch this CVE.