<?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>Mon, 16 Nov 2026 20:16:18 +0000</lastBuildDate>
    <item>
      <title>BREW-cycode-CVE-2026-59951 — MCP Python SDK: Unbounded Session Accumulation in StreamableHTTP Transport Enables Resource Exhaustion</title>
      <link>https://cve.radiocsirt.org/vuln/brew-cycode-cve-2026-59951</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: cycode&lt;/p&gt;
&lt;p&gt;### Summary
In affected versions, a Streamable HTTP server in stateful mode (the default) never reclaimed session state:&lt;/p&gt;
&lt;p&gt;- sessions did not expire;
- a client `DELETE` ended the session but left its entry registered;
- a session whose first request was refused stayed registered with a running task.&lt;/p&gt;
&lt;p&gt;Each session also kept its parsed `initialize` parameters, and the number of sessions was unlimited. A client that could reach the endpoint could grow server memory without bound using ordinary short requests; only a restart reclaimed it.&lt;/p&gt;
&lt;p&gt;### Am I affected?
Yes, if you serve MCP over Streamable HTTP in stateful mode and clients you do not fully trust can reach the endpoint. Stateful mode is the default for:&lt;/p&gt;
&lt;p&gt;- `FastMCP` (1.x)
- `MCPServer` and `Server.streamable_http_app()` (2.x)
- `StreamableHTTPSessionManager`&lt;/p&gt;
&lt;p&gt;Affected versions: 1.8.0 through 1.29.1, and 2.0.0 through 2.1.1.&lt;/p&gt;
&lt;p&gt;Not affected:&lt;/p&gt;
&lt;p&gt;- servers on 1.12.0 or later passing `stateless_http=True` (no sessions are kept)
- servers using only the stdio or SSE transports&lt;/p&gt;
&lt;p&gt;Authentication limits who can open sessions, not how many a token holder can open.&lt;/p&gt;
&lt;p&gt;### Fix
Upgrade to `mcp` 1.30.0 (1.x) or 2.2.0 (2.x) or later. In those versions:&lt;/p&gt;
&lt;p&gt;- a session with no request in flight for `session_idle_timeout` seconds (default 1800) is closed and its ID then answers `404`; open streams and in-progress requests keep it alive;
- at most `max_sessions` sessions exist at once (default 10000); a request that would open another is answered `50…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: cycode&lt;/p&gt;
&lt;p&gt;### Summary
In affected versions, a Streamable HTTP server in stateful mode (the default) never reclaimed session state:&lt;/p&gt;
&lt;p&gt;- sessions did not expire;
- a client `DELETE` ended the session but left its entry registered;
- a session whose first request was refused stayed registered with a running task.&lt;/p&gt;
&lt;p&gt;Each session also kept its parsed `initialize` parameters, and the number of sessions was unlimited. A client that could reach the endpoint could grow server memory without bound using ordinary short requests; only a restart reclaimed it.&lt;/p&gt;
&lt;p&gt;### Am I affected?
Yes, if you serve MCP over Streamable HTTP in stateful mode and clients you do not fully trust can reach the endpoint. Stateful mode is the default for:&lt;/p&gt;
&lt;p&gt;- `FastMCP` (1.x)
- `MCPServer` and `Server.streamable_http_app()` (2.x)
- `StreamableHTTPSessionManager`&lt;/p&gt;
&lt;p&gt;Affected versions: 1.8.0 through 1.29.1, and 2.0.0 through 2.1.1.&lt;/p&gt;
&lt;p&gt;Not affected:&lt;/p&gt;
&lt;p&gt;- servers on 1.12.0 or later passing `stateless_http=True` (no sessions are kept)
- servers using only the stdio or SSE transports&lt;/p&gt;
&lt;p&gt;Authentication limits who can open sessions, not how many a token holder can open.&lt;/p&gt;
&lt;p&gt;### Fix
Upgrade to `mcp` 1.30.0 (1.x) or 2.2.0 (2.x) or later. In those versions:&lt;/p&gt;
&lt;p&gt;- a session with no request in flight for `session_idle_timeout` seconds (default 1800) is closed and its ID then answers `404`; open streams and in-progress requests keep it alive;
- at most `max_sessions` sessions exist at once (default 10000); a request that would open another is answered `50…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-cycode-cve-2026-59951</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1385 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Elles permettent à un attaquant de provoquer…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1385</link>
      <description>certfr-2026-avi-1385</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1385</guid>
    </item>
    <item>
      <title>EUVD-2026-387479</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-387479</link>
      <description>EUVD-2026-387479</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-387479</guid>
    </item>
    <item>
      <title>fkie_cve-2026-59951</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-59951</link>
      <description>&lt;p&gt;The MCP Python SDK, called mcp on PyPI, is a Python implementation of the Model Context Protocol (MCP). From 1.8.0 until 1.30.0 and 2.2.0, stateful Streamable HTTP servers, including FastMCP, MCPServer, Server.streamable_http_app(), and StreamableHTTPSessionManager, retain session entries without an idle expiration or aggregate session-count limit. DELETE, refused opening requests, and completed sessions do not reliably discard their entries, and each entry can retain parsed initialize parameters. A client that can reach the endpoint can therefore create ordinary short requests that grow server memory without bound until restart. Stateless HTTP, stdio, and SSE transports are not affected. This issue is fixed in versions 1.30.0 and 2.2.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The MCP Python SDK, called mcp on PyPI, is a Python implementation of the Model Context Protocol (MCP). From 1.8.0 until 1.30.0 and 2.2.0, stateful Streamable HTTP servers, including FastMCP, MCPServer, Server.streamable_http_app(), and StreamableHTTPSessionManager, retain session entries without an idle expiration or aggregate session-count limit. DELETE, refused opening requests, and completed sessions do not reliably discard their entries, and each entry can retain parsed initialize parameters. A client that can reach the endpoint can therefore create ordinary short requests that grow server memory without bound until restart. Stateless HTTP, stdio, and SSE transports are not affected. This issue is fixed in versions 1.30.0 and 2.2.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-59951</guid>
    </item>
    <item>
      <title>GHSA-84m7-p3x7-pcfv — MCP Python SDK: Unbounded Session Accumulation in StreamableHTTP Transport Enables Resource Exhaustion</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-84m7-p3x7-pcfv</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: mcp&lt;/p&gt;
&lt;p&gt;### Summary
In affected versions, a Streamable HTTP server in stateful mode (the default) never reclaimed session state:&lt;/p&gt;
&lt;p&gt;- sessions did not expire;
- a client `DELETE` ended the session but left its entry registered;
- a session whose first request was refused stayed registered with a running task.&lt;/p&gt;
&lt;p&gt;Each session also kept its parsed `initialize` parameters, and the number of sessions was unlimited. A client that could reach the endpoint could grow server memory without bound using ordinary short requests; only a restart reclaimed it.&lt;/p&gt;
&lt;p&gt;### Am I affected?
Yes, if you serve MCP over Streamable HTTP in stateful mode and clients you do not fully trust can reach the endpoint. Stateful mode is the default for:&lt;/p&gt;
&lt;p&gt;- `FastMCP` (1.x)
- `MCPServer` and `Server.streamable_http_app()` (2.x)
- `StreamableHTTPSessionManager`&lt;/p&gt;
&lt;p&gt;Affected versions: 1.8.0 through 1.29.1, and 2.0.0 through 2.1.1.&lt;/p&gt;
&lt;p&gt;Not affected:&lt;/p&gt;
&lt;p&gt;- servers on 1.12.0 or later passing `stateless_http=True` (no sessions are kept)
- servers using only the stdio or SSE transports&lt;/p&gt;
&lt;p&gt;Authentication limits who can open sessions, not how many a token holder can open.&lt;/p&gt;
&lt;p&gt;### Fix
Upgrade to `mcp` 1.30.0 (1.x) or 2.2.0 (2.x) or later. In those versions:&lt;/p&gt;
&lt;p&gt;- a session with no request in flight for `session_idle_timeout` seconds (default 1800) is closed and its ID then answers `404`; open streams and in-progress requests keep it alive;
- at most `max_sessions` sessions exist at once (default 10000); a request that would open another is answered `50…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: mcp&lt;/p&gt;
&lt;p&gt;### Summary
In affected versions, a Streamable HTTP server in stateful mode (the default) never reclaimed session state:&lt;/p&gt;
&lt;p&gt;- sessions did not expire;
- a client `DELETE` ended the session but left its entry registered;
- a session whose first request was refused stayed registered with a running task.&lt;/p&gt;
&lt;p&gt;Each session also kept its parsed `initialize` parameters, and the number of sessions was unlimited. A client that could reach the endpoint could grow server memory without bound using ordinary short requests; only a restart reclaimed it.&lt;/p&gt;
&lt;p&gt;### Am I affected?
Yes, if you serve MCP over Streamable HTTP in stateful mode and clients you do not fully trust can reach the endpoint. Stateful mode is the default for:&lt;/p&gt;
&lt;p&gt;- `FastMCP` (1.x)
- `MCPServer` and `Server.streamable_http_app()` (2.x)
- `StreamableHTTPSessionManager`&lt;/p&gt;
&lt;p&gt;Affected versions: 1.8.0 through 1.29.1, and 2.0.0 through 2.1.1.&lt;/p&gt;
&lt;p&gt;Not affected:&lt;/p&gt;
&lt;p&gt;- servers on 1.12.0 or later passing `stateless_http=True` (no sessions are kept)
- servers using only the stdio or SSE transports&lt;/p&gt;
&lt;p&gt;Authentication limits who can open sessions, not how many a token holder can open.&lt;/p&gt;
&lt;p&gt;### Fix
Upgrade to `mcp` 1.30.0 (1.x) or 2.2.0 (2.x) or later. In those versions:&lt;/p&gt;
&lt;p&gt;- a session with no request in flight for `session_idle_timeout` seconds (default 1800) is closed and its ID then answers `404`; open streams and in-progress requests keep it alive;
- at most `max_sessions` sessions exist at once (default 10000); a request that would open another is answered `50…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-84m7-p3x7-pcfv</guid>
    </item>
    <item>
      <title>RHSA-2026:92510 — Red Hat Security Advisory: RHOAI 3.4.6 - Red Hat OpenShift AI</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:92510</link>
      <description>&lt;p&gt;sqlite: SQLite: Arbitrary code execution via crafted FTS5 full-text search data sqlite: SQLite: Arbitrary code execution and crash via heap-based buffer overflow in FTS5 RHOAI MaaS: llm-d: MaaS/llm-d inference Gateway: default allowedRoutes.namespaces.from: All allows namespace users to hijack shared model-serving traffic (tokens, prompts, outputs) fast-uri: Fast-uri: Security policy bypass due to URL parsing inconsistency github.com/moby/go-archive: moby/go-archive: Arbitrary file write via link following in tar extraction fast-uri: fast-uri: Host confusion vulnerability via backslash in URI authority golang.org/x/net/html: golang.org/x/net/html: Arbitrary code execution via Cross-Site Scripting cryptography: cryptography Subgroup Attack Due to Missing Subgroup Validation for SECT Curves golang.org/x/net/html: golang: golang.org/x/net/html: Cross-Site Scripting via HTML parsing bypass net/http/internal/http2: golang: golang.org/x/net: Go HTTP/2: Denial of Service via malformed SETTINGS_MAX_FRAME_SIZE frame encoding/asn1: golang: Go encoding/asn1: Denial of Service via excessive recursion in Unmarshal golang.org/x/net/idna: golang: net/http: golang.org/x/net/idna: Privilege escalation via incorrect Punycode label processing golang.org/x/crypto/ssh: golang: golang.org/x/crypto/ssh: Denial of Service due to integer overflow in SSH channel write github.com/open-telemetry/opentelemetry-go: go.opentelemetry.io/otel/baggage: go.opentelemetry.io/otel/propagation: OpenTelemetry-Go:…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;sqlite: SQLite: Arbitrary code execution via crafted FTS5 full-text search data sqlite: SQLite: Arbitrary code execution and crash via heap-based buffer overflow in FTS5 RHOAI MaaS: llm-d: MaaS/llm-d inference Gateway: default allowedRoutes.namespaces.from: All allows namespace users to hijack shared model-serving traffic (tokens, prompts, outputs) fast-uri: Fast-uri: Security policy bypass due to URL parsing inconsistency github.com/moby/go-archive: moby/go-archive: Arbitrary file write via link following in tar extraction fast-uri: fast-uri: Host confusion vulnerability via backslash in URI authority golang.org/x/net/html: golang.org/x/net/html: Arbitrary code execution via Cross-Site Scripting cryptography: cryptography Subgroup Attack Due to Missing Subgroup Validation for SECT Curves golang.org/x/net/html: golang: golang.org/x/net/html: Cross-Site Scripting via HTML parsing bypass net/http/internal/http2: golang: golang.org/x/net: Go HTTP/2: Denial of Service via malformed SETTINGS_MAX_FRAME_SIZE frame encoding/asn1: golang: Go encoding/asn1: Denial of Service via excessive recursion in Unmarshal golang.org/x/net/idna: golang: net/http: golang.org/x/net/idna: Privilege escalation via incorrect Punycode label processing golang.org/x/crypto/ssh: golang: golang.org/x/crypto/ssh: Denial of Service due to integer overflow in SSH channel write github.com/open-telemetry/opentelemetry-go: go.opentelemetry.io/otel/baggage: go.opentelemetry.io/otel/propagation: OpenTelemetry-Go:…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:92510</guid>
    </item>
  </channel>
</rss>
