# CVE-2026-84452 — microsoft winml-cli

> As of 2026-09-03, CVE-2026-84452 is a High-severity (band derived from the CVSS v4.0 score, not stated by the CNA) vulnerability in microsoft winml-cli, CVSS v4.0 8.6, EPSS 0.9% (58.7th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-84452 as of 2026-09-03; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-09-03

## What is CVE-2026-84452?

Windows ML CLI is a command line tool for building portable, performant, and high-quality AI models for Windows ML. Prior to 0.4.0, the src/winml/modelkit/serve/cli_api.py component exposes WinML CLI commands through a localhost HTTP API without authentication and configures the allow_origins setting as a wildcard in both src/winml/modelkit/serve/cli_api.py and src/winml/modelkit/serve/app.py. A malicious website loaded by a user can send cross-origin requests to /v1/cli/build or /v1/cli/config and set the trust_remote_code parameter to true, which is converted to the --trust-remote-code command-line flag without validation. This reaches AutoConfig.from_pretrained with trust_remote_code=True in src/winml/modelkit/loader/_autoconfig.py and imports Python code from an attacker-controlled model repository, resulting in arbitrary code execution as the server user. This issue is fixed in version 0.4.0.

The record classifies CVE-2026-84452 under weakness classes [CWE-942](https://cwe.mitre.org/data/definitions/942.html), [CWE-306](https://intel.threadlinqs.com/cwe/CWE-306). 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 33 days ago.

## Severity and exploitation probability

- **CVSS v4.0 base score:** 8.6 — High (derived from score) (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **EPSS (FIRST):** 0.9% probability of exploitation in the next 30 days, higher than 58.7% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 6.6/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-09-02, last modified 2026-09-03

## Is CVE-2026-84452 being exploited?

It currently carries a trending score of 44 in the Threadlinqs vulnerability feed.

## Affected products and versions

- [microsoft](https://intel.threadlinqs.com/vendors/microsoft): winml-cli

## How to fix CVE-2026-84452

No vendor patch reference has been recorded for CVE-2026-84452 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-84452

No threat campaign in the Threadlinqs corpus currently references CVE-2026-84452, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD, FIRST EPSS. Last verified by Threadlinqs on 2026-09-04. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [github.com](https://github.com/microsoft/winml-cli/security/advisories/GHSA-96p9-rh4f-92cf)

**Other references**

- [github.com](https://github.com/microsoft/winml-cli/pull/1321)
- [github.com (f4073e0ef4700a25b623487e7e45c421ca0b9993)](https://github.com/microsoft/winml-cli/commit/f4073e0ef4700a25b623487e7e45c421ca0b9993)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-84452
Full detection coverage and IOCs for threats exploiting CVE-2026-84452 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp