<?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://cve.radiocsirt.org</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>Sun, 22 Nov 2026 16:00:37 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-408858</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-408858</link>
      <description>EUVD-2026-408858</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-408858</guid>
    </item>
    <item>
      <title>fkie_cve-2026-130007</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-130007</link>
      <description>&lt;p&gt;k8s-mcp-server manages Kubernetes clusters through the Model Context Protocol. Prior to 1.1.0, SERVER_MODE defaults to SSE, with the listener on 0.0.0.0:8080, but main.go creates the SSE server without an authentication option or context function. The GET /sse handler creates a sessionId that is only a correlation value, and the POST /message handler accepts a loadable sessionId without an authorization or Origin check before dispatching tools/call; consequently, any client able to reach the port can enumerate and invoke registered Kubernetes tools without credentials. Read-only mode is disabled by default, leaving write-capable Kubernetes tools available to run with the server&amp;#39;s configured cluster privileges. This issue is fixed in version 1.1.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;k8s-mcp-server manages Kubernetes clusters through the Model Context Protocol. Prior to 1.1.0, SERVER_MODE defaults to SSE, with the listener on 0.0.0.0:8080, but main.go creates the SSE server without an authentication option or context function. The GET /sse handler creates a sessionId that is only a correlation value, and the POST /message handler accepts a loadable sessionId without an authorization or Origin check before dispatching tools/call; consequently, any client able to reach the port can enumerate and invoke registered Kubernetes tools without credentials. Read-only mode is disabled by default, leaving write-capable Kubernetes tools available to run with the server&amp;#39;s configured cluster privileges. This issue is fixed in version 1.1.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-130007</guid>
    </item>
    <item>
      <title>GHSA-m932-63jc-4jqq — k8s-mcp-server: Missing authentication on default SSE/HTTP transport allows unauthenticated Kubernetes tool execution</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-m932-63jc-4jqq</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/reza-gholizade/k8s-mcp-server&lt;/p&gt;
&lt;p&gt;## Summary
When k8s-mcp-server runs in its default SSE transport mode, the MCP `tools/call`
endpoint is dispatched with no authentication, session token, or Origin check.
Any client that can reach the listening port can enumerate and invoke the
server&amp;#39;s Kubernetes tools (including destructive/write tools) without credentials,
executing with the server&amp;#39;s configured cluster privileges.&lt;/p&gt;
&lt;p&gt;## Affected
Commit be87a6dd72bb6ec1d4886b8548843b99a4638b12 (Merge PR #130)
MCP library: github.com/mark3labs/mcp-go v0.57.0
Default mode: sse (SERVER_MODE default), default port 8080, bind 0.0.0.0&lt;/p&gt;
&lt;p&gt;## Root cause (static trace: handleSSE -&amp;gt; handleMessage -&amp;gt; tools/call)
- main.go L129: `server.NewSSEServer(s)` is created with no auth option and no
  contextFunc; L130 `sse.Start(&amp;#34;:&amp;#34;+port)` binds all interfaces (0.0.0.0).
- mcp-go sse.go handleSSE (GET /sse): no auth header check; the server mints a
  sessionId for any caller. The sessionId is a correlation value, not a credential.
- handleMessage (POST /message): the only gates are method==POST and a loadable
  sessionId. No Authorization/Bearer/token/Origin/CSRF check before
  `s.server.HandleMessage(ctx, rawMessage)` dispatches to the tools/call handler.
- Only `Access-Control-Allow-Origin: *` is present (CORS relaxation, not auth).
Write tools (Create/Delete/RolloutRestart, Helm Install/Upgrade/Uninstall/Rollback)
are all registered unless `-read-only` is set (default readOnly=false).&lt;/p&gt;
&lt;p&gt;## Runtime reproduction (no auth headers on any request)
S…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/reza-gholizade/k8s-mcp-server&lt;/p&gt;
&lt;p&gt;## Summary
When k8s-mcp-server runs in its default SSE transport mode, the MCP `tools/call`
endpoint is dispatched with no authentication, session token, or Origin check.
Any client that can reach the listening port can enumerate and invoke the
server&amp;#39;s Kubernetes tools (including destructive/write tools) without credentials,
executing with the server&amp;#39;s configured cluster privileges.&lt;/p&gt;
&lt;p&gt;## Affected
Commit be87a6dd72bb6ec1d4886b8548843b99a4638b12 (Merge PR #130)
MCP library: github.com/mark3labs/mcp-go v0.57.0
Default mode: sse (SERVER_MODE default), default port 8080, bind 0.0.0.0&lt;/p&gt;
&lt;p&gt;## Root cause (static trace: handleSSE -&amp;gt; handleMessage -&amp;gt; tools/call)
- main.go L129: `server.NewSSEServer(s)` is created with no auth option and no
  contextFunc; L130 `sse.Start(&amp;#34;:&amp;#34;+port)` binds all interfaces (0.0.0.0).
- mcp-go sse.go handleSSE (GET /sse): no auth header check; the server mints a
  sessionId for any caller. The sessionId is a correlation value, not a credential.
- handleMessage (POST /message): the only gates are method==POST and a loadable
  sessionId. No Authorization/Bearer/token/Origin/CSRF check before
  `s.server.HandleMessage(ctx, rawMessage)` dispatches to the tools/call handler.
- Only `Access-Control-Allow-Origin: *` is present (CORS relaxation, not auth).
Write tools (Create/Delete/RolloutRestart, Helm Install/Upgrade/Uninstall/Rollback)
are all registered unless `-read-only` is set (default readOnly=false).&lt;/p&gt;
&lt;p&gt;## Runtime reproduction (no auth headers on any request)
S…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-m932-63jc-4jqq</guid>
    </item>
  </channel>
</rss>
