ManageIQ / ManageIQ/vmware_web_service
CVE-2026-67431 (High) detected in mcp-0.9.0.gem
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 7
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
CVE-2026-67431 - High Severity Vulnerability
Vulnerable Library - mcp-0.9.0.gem
The official Ruby SDK for Model Context Protocol servers and clients
Library home page: https://rubygems.org/gems/mcp-0.9.0.gem
Path to dependency file: /Gemfile.lock
Path to vulnerable library: /vendor/cache/mcp-0.9.0.gem
Dependency Hierarchy:
- manageiq-style-1.6.0.gem (Root Library)
- rubocop-1.85.1.gem
- ❌ mcp-0.9.0.gem (Vulnerable Library)
- rubocop-1.85.1.gem
Found in base branch: master
Vulnerability Details
MCP Ruby SDK is the official Ruby SDK for Model Context Protocol servers and clients. Prior to 0.23.0, MCP::Server::Transports::StreamableHTTPTransport in the mcp gem does not bind a session ID to a session owner, allowing an attacker with a stolen session ID to send tools/call requests that execute in the victim's session. This issue is fixed in version 0.23.0.
Publish Date: 2026-07-29
URL: CVE-2026-67431
CVSS 3 Score Details (8.2)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: Low
Suggested Fix
Type: Upgrade version
Origin: https://github.com/advisories/GHSA-5p9g-j988-pcwv
Release Date: 2026-07-29
Fix Resolution: mcp - 0.23.0
Step up your Open Source Security Game with Mend here
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting Gemfile.lock and the vendored mcp-0.9.0.gem dependency shown in the report, including its path through rubocop. Update the resolved mcp version to 0.23.0 or newer, then verify the dependency files no longer select the vulnerable release and that the reported CVE is cleared.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- security
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 72/100