Threats / Microsoft / CVE-2026-21533
CVE-2026-21533
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Microsoft Windows vulnerability
Microsoft Windows Remote Desktop Services contains an improper privilege management vulnerability allowing authorized attackers to elevate privileges locally.
Verdict
Today item — known-exploited.
An authenticated local attacker can exploit improper privilege controls in Windows Remote Desktop Services to gain elevated system privileges. Active exploitation in the wild indicates practical threat.
CISA KEV Yes · 2026-02-105EPSS 0.03846 (verify live)6CVSS 7.83CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
5 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 2026-02-10).
Probability (EPSS)
EPSS 0.03846 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 7.8 (CVSS:3.1/AV:L/AC:L/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-269 Improper Privilege Management — weakness family: Authorization / access control.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 authenticate to a Windows system with standard user privileges.
Business
Legitimate user credentials provide initial system access.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I interact with Remote Desktop Services components to trigger the privilege management flaw.
Business
Authorized system access becomes a pivot point for lateral movement.
3
Lateral reach — past segmentation narrative 3
Attacker
I escalate my privileges to administrator or system level through the vulnerability.
Business
Attacker gains control equivalent to system administrator, enabling full system compromise.
4
Data at risk — exfiltration narrative 4
Attacker
I execute arbitrary code and modify system configurations with elevated privileges.
Business
Malware installation, data exfiltration, and persistent backdoor establishment become possible.
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