PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-84452 microsoft CVE debrief

The Windows ML CLI tool, prior to version 0.4.0, is vulnerable to arbitrary code execution due to a lack of authentication and validation in its localhost HTTP API. This issue allows a malicious website to send cross-origin requests, potentially leading to code execution as the server user. The vulnerability is addressed in version 0.4.0. Users of the Windows ML CLI tool, especially in server environments, should be aware of this vulnerability and take steps to mitigate it. Security teams and administrators should prioritize this issue due to its high CVSS score and potential for exploitation.

Vendor
microsoft
Product
winml-cli
CVSS
HIGH 8.6
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-02
Original CVE updated
2026-09-03
Advisory published
2026-09-02
Advisory updated
2026-09-03

Who should care

Users of the Windows ML CLI tool, particularly those who use the tool in a server environment, should be aware of this vulnerability and take steps to mitigate it. Additionally, security teams and administrators responsible for monitoring and patching vulnerabilities should prioritize this issue due to its high CVSS score and potential for exploitation.

Technical summary

The Windows ML CLI tool is vulnerable to arbitrary code execution due to a lack of authentication and validation in the localhost HTTP API. The src/winml/modelkit/serve/cli_api.py component exposes WinML CLI commands without authentication, allowing a malicious website to send cross-origin requests and set the trust_remote_code parameter to true, leading to code execution as the server user. This issue is fixed in version 0.4.0.

Defensive priority

High-priority defensive actions are required to address this vulnerability, as it allows for arbitrary code execution.

Recommended defensive actions

  • Verify and apply the patch to update the Windows ML CLI tool to version 0.4.0 or later.
  • Restrict access to the localhost HTTP API to prevent unauthorized requests.
  • Monitor for suspicious activity and implement compensating controls to detect potential exploitation attempts.
  • Review system logs for signs of exploitation.
  • Implement additional security measures such as network segmentation.
  • Conduct a thorough risk assessment to identify potential vulnerabilities.
  • Develop an incident response plan in case of exploitation.

Evidence notes

Evidence from the CVE Program and NVD suggests that the Windows ML CLI tool is vulnerable to arbitrary code execution due to a lack of authentication and validation in the localhost HTTP API. The src/winml/modelkit/serve/cli_api.py component exposes WinML CLI commands without authentication, allowing a malicious website to send cross-origin requests and set the trust_remote_code parameter to true, leading to code execution as the server user.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-84452 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-84452

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-84452 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-84452

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.