CVE-2026-84452

HIGHPre-NVD 8.68.6—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.9%, top 40% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
8.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.6Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.6
EG Score
8.6(medium)
EG Risk
55(Track*)
EG Risk 55/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity86% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
60%
KEV
Not listed

Published

September 2, 2026

Last Modified

September 9, 2026

Advisory Details (3)

Auto-updated Sep 2, 2026
🔬 Proof of concept available. Patch available. Sources: github_pr, github_commit, github.
github_commit

commit f4073e0ef470 (microsoft/winml-cli)

Fix landed in microsoft/winml-cli commit f4073e0ef470 — awaiting tagged release

https://github.com/microsoft/winml-cli/commit/f4073e0ef4700a25b623487e7e45c421ca0b9993
github_pr

fix(serve): harden CLI API security boundaries

Fix merged in microsoft/winml-cli PR #1321 on 2026-08-21 — awaiting tagged release

https://github.com/microsoft/winml-cli/pull/1321
github Patch Available🟡 PoC Available

CORS misconfig enables localhost RCE · Advisory · microsoft/winml-cli · GitHub

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

Vendor Advisories for CVE-2026-84452(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
winml-cli0.1.0, 0.2.0, 0.3.0, 0.3.10.4.0—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 05:31 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 20:37 UTCEG score recompute
  4. 2026-09-17 19:32 UTCEPSS rescore
  5. 2026-09-16 18:36 UTCEG score recompute
  6. 2026-09-16 14:09 UTCEPSS rescore
  7. 2026-09-16 06:39 UTCEG score recompute
  8. 2026-09-16 05:15 UTCEPSS rescore
  9. 2026-09-15 08:49 UTCEG score recompute
  10. 2026-09-15 03:12 UTCEPSS rescore
  11. 2026-09-15 03:12 UTCEPSS rescore
  12. 2026-09-14 00:01 UTCEG score recompute
  13. 2026-09-12 15:16 UTCEG score recompute
  14. 2026-09-11 17:26 UTCEG score recompute
  15. 2026-09-11 14:53 UTCEPSS rescore
  16. 2026-09-11 14:53 UTCEPSS rescore
  17. 2026-09-10 19:00 UTCEG score recompute
  18. 2026-09-08 23:11 UTCEG score recompute
  19. 2026-09-08 22:01 UTCEPSS rescore
  20. 2026-09-07 20:10 UTCEG score recompute
  21. 2026-09-06 22:14 UTCEG score recompute
  22. 2026-09-06 13:48 UTCEPSS rescore
  23. 2026-09-06 00:23 UTCEG score recompute
  24. 2026-09-05 15:31 UTCEPSS rescore
  25. 2026-09-04 15:35 UTCEG score recompute
Show 6 more
  1. 2026-09-04 05:07 UTCEPSS rescore
  2. 2026-09-03 17:39 UTCEG score recompute
  3. 2026-09-03 16:24 UTCEG score recompute
  4. 2026-09-02 20:21 UTCEG score recompute
  5. 2026-09-02 19:30 UTCEG score recompute
  6. 2026-09-02 19:30 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-84452?
CVE-2026-84452 is a high vulnerability published on September 2, 2026. 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/cliapi.py component exposes WinML CLI commands through a localhost HTTP API without authentication and configures the alloworigins setting…
When was CVE-2026-84452 disclosed?
CVE-2026-84452 was first published in the National Vulnerability Database on September 2, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-84452 actively exploited?
CVE-2026-84452 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 40.5% of all scored CVEs.
What is the CVSS score of CVE-2026-84452?
CVE-2026-84452 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2026-84452?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-84452, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-84452

Explore →

Is Your Infrastructure Affected by CVE-2026-84452?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs