CVE-2026-48989

HIGHPre-NVD 8.98.9—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 68% 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
8.9
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.9Exploit: NoneExposed: 0

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

Windows-MCP is an open-source project that integrates AI agents with Windows. In versions prior to 0.7.5, certain HTTP modes exposed the MCP control plane without authentication while enabling wildcard CORS (allow_origins=*, allow_methods=*, allow_headers=*). Because the same server also exposed a PowerShell tool that executes caller-controlled commands as the Windows user running Windows-MCP, attackers could reach the control plane from arbitrary origins or non-browser clients and achieve arbitrary PowerShell execution. This issue was fixed in version 0.7.5.

CVSS v3
8.9
EG Score
8.9(medium)
EPSS
31.8%
KEV
Not listed

Published

June 17, 2026

Last Modified

June 23, 2026

Advisory Details (2)

Auto-updated Jun 17, 2026
Patch available. Sources: github, github_release.
github Patch Available

HTTP transports expose unauthenticated PowerShell control with wildcard CORS · Advisory · CursorTouch/Windows-MCP · GitHub

https://github.com/CursorTouch/Windows-MCP/security/advisories/GHSA-vrxg-gm77-7q5g
github_release Patch Available

v0.7.5 — Security patch: CORS & DNS rebinding (GHSA-vrxg-gm77-7q5g)

Patch available: CursorTouch/Windows-MCP v0.7.5

https://github.com/CursorTouch/Windows-MCP/releases/tag/v0.7.5

Vendor Advisories for CVE-2026-48989(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
windows-mcp0.6.5 ... 0.7.4 (9 versions)0.7.5—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 0× in last 7d / 0× 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-07-11 08:27 UTCEPSS rescore
  2. 2026-07-11 00:33 UTCEG score recompute
  3. 2026-07-10 11:28 UTCEG score recompute
  4. 2026-07-09 22:46 UTCEG score recompute
  5. 2026-07-09 19:10 UTCEPSS rescore
  6. 2026-07-09 10:03 UTCEG score recompute
  7. 2026-07-08 21:20 UTCEG score recompute
  8. 2026-07-08 15:16 UTCEPSS rescore
  9. 2026-07-08 08:36 UTCEG score recompute
  10. 2026-07-07 19:54 UTCEG score recompute
  11. 2026-07-07 13:46 UTCEPSS rescore
  12. 2026-07-07 02:36 UTCEG score recompute
  13. 2026-07-06 16:27 UTCEPSS rescore
  14. 2026-07-06 13:54 UTCEG score recompute
  15. 2026-07-06 02:23 UTCEPSS rescore
  16. 2026-07-06 00:26 UTCEG score recompute
  17. 2026-07-05 11:42 UTCEG score recompute
  18. 2026-07-05 02:30 UTCEPSS rescore
  19. 2026-07-04 22:59 UTCEG score recompute
  20. 2026-07-04 10:18 UTCEG score recompute
  21. 2026-07-04 06:31 UTCEPSS rescore
  22. 2026-07-03 21:34 UTCEG score recompute
  23. 2026-07-03 08:52 UTCEG score recompute
  24. 2026-07-02 20:11 UTCEG score recompute
  25. 2026-07-02 07:25 UTCEG score recompute
Show 50 more
  1. 2026-07-01 18:43 UTCEG score recompute
  2. 2026-07-01 15:07 UTCEPSS rescore
  3. 2026-07-01 06:01 UTCEG score recompute
  4. 2026-06-30 23:22 UTCEPSS rescore
  5. 2026-06-30 17:19 UTCEG score recompute
  6. 2026-06-30 04:29 UTCEG score recompute
  7. 2026-06-29 15:46 UTCEG score recompute
  8. 2026-06-29 14:06 UTCEPSS rescore
  9. 2026-06-29 14:06 UTCEPSS rescore
  10. 2026-06-29 03:01 UTCEG score recompute
  11. 2026-06-28 14:19 UTCEG score recompute
  12. 2026-06-28 14:07 UTCEPSS rescore
  13. 2026-06-28 04:56 UTCEPSS rescore
  14. 2026-06-28 04:56 UTCEPSS rescore
  15. 2026-06-28 01:37 UTCEG score recompute
  16. 2026-06-27 12:51 UTCEG score recompute
  17. 2026-06-27 03:08 UTCEPSS rescore
  18. 2026-06-27 00:09 UTCEG score recompute
  19. 2026-06-26 11:27 UTCEG score recompute
  20. 2026-06-25 22:20 UTCEG score recompute
  21. 2026-06-25 13:49 UTCEPSS rescore
  22. 2026-06-25 09:38 UTCEG score recompute
  23. 2026-06-24 20:56 UTCEG score recompute
  24. 2026-06-24 14:05 UTCEPSS rescore
  25. 2026-06-24 08:14 UTCEG score recompute
  26. 2026-06-23 21:33 UTCEPSS rescore
  27. 2026-06-23 21:33 UTCEPSS rescore
  28. 2026-06-23 19:28 UTCEG score recompute
  29. 2026-06-23 06:46 UTCEG score recompute
  30. 2026-06-22 18:03 UTCEG score recompute
  31. 2026-06-22 14:25 UTCEPSS rescore
  32. 2026-06-22 14:25 UTCEPSS rescore
  33. 2026-06-22 05:06 UTCEG score recompute
  34. 2026-06-21 16:23 UTCEG score recompute
  35. 2026-06-21 14:56 UTCEPSS rescore
  36. 2026-06-21 14:56 UTCEPSS rescore
  37. 2026-06-21 03:39 UTCEG score recompute
  38. 2026-06-21 01:59 UTCEPSS rescore
  39. 2026-06-21 01:59 UTCEPSS rescore
  40. 2026-06-20 14:56 UTCEG score recompute
  41. 2026-06-20 02:09 UTCEG score recompute
  42. 2026-06-19 19:26 UTCEPSS rescore
  43. 2026-06-19 19:26 UTCEPSS rescore
  44. 2026-06-19 13:25 UTCEG score recompute
  45. 2026-06-19 00:44 UTCEG score recompute
  46. 2026-06-18 17:52 UTCEPSS rescore
  47. 2026-06-18 17:52 UTCEPSS rescore
  48. 2026-06-18 12:01 UTCEG score recompute
  49. 2026-06-17 23:17 UTCEG score recompute
  50. 2026-06-17 23:16 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-48989?
CVE-2026-48989 is a high vulnerability published on June 17, 2026. Windows-MCP is an open-source project that integrates AI agents with Windows. In versions prior to 0.7.5, certain HTTP modes exposed the MCP control plane without authentication while enabling wildcard CORS (alloworigins=*, allowmethods=, allow_headers=). Because the same server also exposed a…
When was CVE-2026-48989 disclosed?
CVE-2026-48989 was first published in the National Vulnerability Database on June 17, 2026, with the most recent update on June 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48989 actively exploited?
CVE-2026-48989 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 31.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-48989?
CVE-2026-48989 has a CVSS v3 base score of 8.9 (NVD).
How do I remediate CVE-2026-48989?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48989, 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-48989

Explore →

Is Your Infrastructure Affected by CVE-2026-48989?

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

Start Free Scan →Browse All CVEs