CVE-2022-21907 — Windows 10
CRITICALCVE-2022-21907 is a critical-severity (CVSS 9.8) remote code execution vulnerability in microsoft windows 10. 23 public exploit references exist, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.
HTTP Protocol Stack Remote Code Execution Vulnerability
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2022-21907.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2022-21907 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).
Where this sits among everything scored
Of 394,415 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.
Description
HTTP Protocol Stack Remote Code Execution Vulnerability
Affected Products
windows 10microsoftwindows 11microsoftwindows servermicrosoftwindows server 2019microsoftResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Windows 10 v21H1 - HTTP Protocol Stack Remote Code Execution
by nu11secur1ty · Jul 7, 2023
Detection & mitigation playbook
Vendor / applianceDetect
Inventory every microsoft windows 10 deployment and check each version against the affected-products list above.
Remediation status
No patch has shipped for CVE-2022-21907 yet — track the microsoft windows 10 advisory for a fixed release and apply the workarounds below in the meantime.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.
Frequently Asked Questions
Is CVE-2022-21907 being exploited in your environment?
Detect and block the exploit chain at execution, on systems you cannot patch yet.