CVE-2026-84452
Unauthenticated RCE in Windows ML CLI via localhost HTTP API and wildcard CORS
Is CVE-2026-84452 being exploited?
Not confirmed. CVE-2026-84452 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.95% probability of exploitation in the next 30 days.
How severe is CVE-2026-84452?
CVE-2026-84452 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-84452?
Yes. A fix has been recorded for CVE-2026-84452. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-84452 affect?
CVE-2026-84452 affects winml-cli (<0.4.0), Windows ML CLI serve endpoint, Systems running WinML CLI local HTTP server. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-84452?
Upgrade to winml-cli v0.4.0 or disable/block the CLI 'serve' HTTP endpoint until patched
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated remote code execution as the server user by sending cross-origin requests that set trust_remote_code, causing attacker-controlled code import.
Immediate action required
- affected< 0.4.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.