Threats / Microsoft / CVE-2023-32046
CVE-2023-32046
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Microsoft Windows vulnerability
Microsoft Windows MSHTML Platform vulnerability allows privilege escalation. Actively exploited in the wild with moderate exploitation likelihood.
Verdict
Today item — known-exploited.
An unspecified privilege escalation flaw in Windows MSHTML Platform has been observed in active exploitation. The moderate EPSS score and confirmed wild exploitation indicate meaningful risk to Windows systems, though specific attack vectors remain undisclosed.
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
4 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 2023-07-11).
Probability (EPSS)
EPSS 0.09083 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Microsoft, Windows. Confirm exact fixed builds in the vendor advisory.
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 craft or deliver malicious content targeting the MSHTML rendering engine to trigger the vulnerability.
Business
Attackers gain elevated system privileges, enabling lateral movement and persistent compromise of affected Windows endpoints.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I escalate from a lower-privileged process context to system or administrator level through the MSHTML flaw.
Business
Compromised systems face increased risk of data exfiltration, malware installation, and operational disruption across the organization.
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