ManageIQ / ManageIQ/amazon_ssa_support
CVE-2026-63119 (Medium) detected in mcp-0.9.0.gem
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 2
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
CVE-2026-63119 - Medium 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-performance-1.26.1.gem
- rubocop-1.85.1.gem
- ❌ mcp-0.9.0.gem (Vulnerable Library)
- rubocop-1.85.1.gem
- rubocop-performance-1.26.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::StdioTransport and MCP::Client::Stdio in the mcp gem use IO#gets without a byte limit, allowing a peer that sends data without a newline to exhaust process memory. This issue is fixed in version 0.23.0.
Publish Date: 2026-07-29
URL: CVE-2026-63119
CVSS 3 Score Details (6.2)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
Suggested Fix
Type: Upgrade version
Origin: https://github.com/advisories/GHSA-7683-3w9x-ch42
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 with /Gemfile.lock and the vendored /vendor/cache/mcp-0.9.0.gem entry, then review the dependency hierarchy in the issue. Upgrade mcp to 0.23.0 or later and refresh the recorded dependency files. Done means the vulnerable 0.9.0 library is no longer present and the CVE is resolved.
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
- 76/100