<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 07 Oct 2026 19:53:15 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-48989 — Windows-MCP: HTTP transports expose unauthenticated PowerShell control with wildcard CORS</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-48989</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CursorTouch Windows-MCP&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CursorTouch Windows-MCP&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-48989</guid>
    </item>
    <item>
      <title>GHSA-vrxg-gm77-7q5g — Windows-MCP: HTTP transports expose unauthenticated PowerShell control with wildcard CORS</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-vrxg-gm77-7q5g</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: windows-mcp&lt;/p&gt;
&lt;p&gt;HTTP transports expose unauthenticated PowerShell control with wildcard CORS&lt;/p&gt;
&lt;p&gt;There is an issue in the SSE and Streamable HTTP transport modes. The default stdio mode is not affected, but the documented HTTP modes expose the MCP control plane without authentication and add wildcard CORS handling around it. The same server exposes the `PowerShell` tool, which executes caller-controlled commands as the Windows user running Windows-MCP.&lt;/p&gt;
&lt;p&gt;Relevant source:&lt;/p&gt;
&lt;p&gt;- `src/windows_mcp/__main__.py:37-42`: `_http_middleware()` installs `OptionsMiddleware` and `CORSMiddleware` with `allow_origins=[&amp;#34;*&amp;#34;]`, `allow_methods=[&amp;#34;*&amp;#34;]`, and `allow_headers=[&amp;#34;*&amp;#34;]`.
- `src/windows_mcp/__main__.py:45-72`: `OptionsMiddleware` responds to every `OPTIONS` request with wildcard `Access-Control-Allow-Origin`, `Access-Control-Allow-Methods`, and `Access-Control-Allow-Headers`.
- `src/windows_mcp/__main__.py:75-113`: `_build_mcp()` constructs `FastMCP(name=&amp;#34;windows-mcp&amp;#34;, ...)` without an auth provider.
- `src/windows_mcp/__main__.py:139-151`: both `sse` and `streamable-http` call `mcp.run(...)` with that middleware and no application-level auth/security settings.
- `src/windows_mcp/tools/shell.py:10-24`: registers the `PowerShell` tool and passes caller-controlled `command` to `PowerShellExecutor.execute_command`.
- `src/windows_mcp/desktop/powershell.py:176-204`: executes that command through PowerShell `-EncodedCommand`.
- `README.md:421-424` and `433-434`: documents the HTTP transports and describes Streamabl…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: windows-mcp&lt;/p&gt;
&lt;p&gt;HTTP transports expose unauthenticated PowerShell control with wildcard CORS&lt;/p&gt;
&lt;p&gt;There is an issue in the SSE and Streamable HTTP transport modes. The default stdio mode is not affected, but the documented HTTP modes expose the MCP control plane without authentication and add wildcard CORS handling around it. The same server exposes the `PowerShell` tool, which executes caller-controlled commands as the Windows user running Windows-MCP.&lt;/p&gt;
&lt;p&gt;Relevant source:&lt;/p&gt;
&lt;p&gt;- `src/windows_mcp/__main__.py:37-42`: `_http_middleware()` installs `OptionsMiddleware` and `CORSMiddleware` with `allow_origins=[&amp;#34;*&amp;#34;]`, `allow_methods=[&amp;#34;*&amp;#34;]`, and `allow_headers=[&amp;#34;*&amp;#34;]`.
- `src/windows_mcp/__main__.py:45-72`: `OptionsMiddleware` responds to every `OPTIONS` request with wildcard `Access-Control-Allow-Origin`, `Access-Control-Allow-Methods`, and `Access-Control-Allow-Headers`.
- `src/windows_mcp/__main__.py:75-113`: `_build_mcp()` constructs `FastMCP(name=&amp;#34;windows-mcp&amp;#34;, ...)` without an auth provider.
- `src/windows_mcp/__main__.py:139-151`: both `sse` and `streamable-http` call `mcp.run(...)` with that middleware and no application-level auth/security settings.
- `src/windows_mcp/tools/shell.py:10-24`: registers the `PowerShell` tool and passes caller-controlled `command` to `PowerShellExecutor.execute_command`.
- `src/windows_mcp/desktop/powershell.py:176-204`: executes that command through PowerShell `-EncodedCommand`.
- `README.md:421-424` and `433-434`: documents the HTTP transports and describes Streamabl…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-vrxg-gm77-7q5g</guid>
    </item>
  </channel>
</rss>
