Threats / Microsoft / CVE-2025-24983
CVE-2025-24983
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Microsoft Windows vulnerability
A use-after-free vulnerability in Windows Win32 Kernel Subsystem allows authorized local attackers to elevate privileges. The flaw is actively exploited in the wild.
Verdict
Today item — known-exploited.
Authorized local attackers can exploit this use-after-free to gain elevated privileges on Windows systems. Active exploitation in the wild increases risk. Patch deployment is recommended for affected Windows installations.
CISA KEV Yes · 2025-03-115EPSS 0.01298 (verify live)6CVSS 73CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
10 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-03-11).
Probability (EPSS)
EPSS 0.01298 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 7 (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C) · Affected: Microsoft, Windows. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-416 Use After Free — weakness family: Memory safety.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog the same day the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I gain initial access as a standard user or service account on a Windows system.
Business
An attacker establishes a foothold with limited privileges, creating opportunity for lateral movement or persistence.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I trigger the use-after-free condition in the Win32 Kernel Subsystem through a crafted local operation.
Business
The vulnerability is weaponized through a specific sequence of kernel interactions that the organization may not detect.
3
Lateral reach — past segmentation narrative 3
Attacker
I execute code with elevated system privileges after successful exploitation.
Business
The attacker gains administrative or SYSTEM-level control, enabling full system compromise and data exfiltration.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05