Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.6amended

Windows ML CLI: CORS misconfig enables localhost RCE

CVE-2026-84452GHSA-96p9-rh4f-92cf

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (winml-cli 0.4.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.6 · 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 · score source
EPSS
  • CVE-2026-84452: 1.61% estimated exploitation activity in the next 30 days; percentile 75.94 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Case Description: MSRC Notes: Attachments: 1 file(s) attached (1 mp4) Summary: The vulnerability lies in the 'serve/cliapi.py' component of the 'winml-cli' project, which exposes all winml CLI commands over HTTP without authentication. Although it binds to localhost by default, it sets 'alloworigins' to a wildcard, allowing any website to interact with the endpoint. This, combined with the '--trust-remote-code' flag in 'build' and 'config' commands, enables an attacker to execute arbitrary code by hosting a malicious model repository. The root cause is the lack of proper authentication and validation of the 'trustremotecode' parameter, leading to Remote Code Execution (RCE). Finder Description: WARNING: Original content contained invalid characters. Please see original submission in the event that the characters removed are relevant for the PoC. serve/cliapi.py exposes every winml CLI command over HTTP with no authentication. That's defensible on its own - it binds 127.0.0.1 by…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-96p9-rh4f-92cf

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GHSA-96p9-rh4f-92cf

  4. Revision 1 · created ·

    Published from ghsa record GHSA-96p9-rh4f-92cf

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-84452

Advisory: Windows ML CLI: CORS misconfig enables localhost RCE
IDs: CVE-2026-84452, GHSA-96p9-rh4f-92cf
Record: https://patchnext.com/advisories/cve-2026-84452 (revision 4, source checked 26 Oct 2026, 13:51 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: winml-cli 0.4.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI winml-cli: affected < 0.4.0; fixed in 0.4.0

## Suggested inspection (read-only)
- `python -m pip show winml-cli`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on winml-cli.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-96p9-rh4f-92cf (GitHub-reviewed advisory GHSA-96p9-rh4f-92cf lists affected ranges: PyPI winml-cli >=0 <0.4.0)
- Verified: https://osv.dev/vulnerability/GHSA-96p9-rh4f-92cf (OSV record GHSA-96p9-rh4f-92cf lists affected ranges: PyPI winml-cli >=0 <0.4.0 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…