Is CVE-2026-67431 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-67431 being exploited in the wild.

How severe is CVE-2026-67431?

High severity, with a CVSS score of 4, published 29 July 2026.

Which products and versions are affected?

mcp (RubyGems) ECOSYSTEM:introduced=0,fixed=0.23.0.

Is there a fix for CVE-2026-67431?

Yes. mcp (RubyGems): upgrade to 0.23.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-67431 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-67431?

Check whether you run Model Context Protocol Ruby SDK or mcp (RubyGems) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-67431: modelcontextprotocol ruby-sdk session hijacking in StreamableHTTPTransport

CVE-2026-67431 · Severity: high · CVSS 4 · Published 2026-07-29

The Ruby SDK for the Model Context Protocol (MCP) contains a vulnerability where it fails to verify the ownership of active sessions. An attacker who obtains a valid session ID can send unauthorized commands to the server, causing the server to execute tools on behalf of the victim. This can lead to unauthorized data modification or state changes within the victim's session without their knowledge.

Technologies: mcp (RubyGems). Vendors: Model Context Protocol, RubyGems.

Quick answers

Is CVE-2026-67431 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-67431 being exploited in the wild.
How severe is CVE-2026-67431?: High severity, with a CVSS score of 4, published 29 July 2026.
Which products and versions are affected?: mcp (RubyGems) ECOSYSTEM:introduced=0,fixed=0.23.0.
Is there a fix for CVE-2026-67431?: Yes. mcp (RubyGems): upgrade to 0.23.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-67431 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-67431?: Check whether you run Model Context Protocol Ruby SDK or mcp (RubyGems) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

mcp (RubyGems): upgrade to 0.23.0 or later
```
bundle update mcp
```

Technical details

A session poisoning vulnerability exists in the `StreamableHttpTransport` and SSE implementation of the Ruby MCP SDK. The root cause is a lack of validation binding session IDs to specific users or connections. An attacker who obtains a victim's session ID can send POST requests to the `/messages/:session_id` endpoint to trigger tool executions. The server processes these requests and sends the resulting tool output to the victim's Server-Sent Events (SSE) stream, effectively hijacking the session's integrity. This issue is addressed in version 0.23.0 by implementing session ownership checks.

Affected products

Model Context Protocol (MCP) Ruby SDK mcp <= 0.22.0

Identifiers

CVE-2026-67431
GHSA-5p9g-j988-pcwv

Timeline

2026-07-08: disclosed: Initial report/publication on GitHub
2026-07-29: other: NVD publication
2026-07-30: patched: Version 0.23.0 released and advisory updated

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.