CVE-2026-8355
MediumCVSS 5.4Exploitation Probability (EPSS)
Low risk7th percentile - higher than 7% of all known CVEs
Summary
A Server-Side Request Forgery (SSRF) vulnerability in IBM ContextForge MCP Gateway versions 0.1.0 through 1.0.5. An authenticated user with gateway creation privileges can perform arbitrary HTTP POST requests to internal network resources and cloud metadata endpoints by supplying a malicious oauth_config.token_url parameter during OAuth-enabled gateway registration.
Risk Assessment
An attacker could access internal services, cloud metadata (AWS, GCP, Azure), or localhost-bound services, potentially leading to data leakage or further exploitation. The vulnerability bypasses existing SSRF protections for the gateway.url field.
Recommendation
Update IBM ContextForge MCP Gateway to a version later than 1.0.5, which contains the fix. Additionally, consider validating the oauth_config.token_url parameter and restricting access to internal resources.
Other vulnerabilities in IBM ContextForge MCP Gateway
See all- CVE-2026-78573Critical
IBM ContextForge MCP Gateway versions 1.0.0 through 1.0.7 allow a remote attacker to gain administrative access due to the use of default credentials.
- CVE-2026-77825Medium
IBM ContextForge MCP Gateway 1.0.0 through 1.0.8 was vulnerable to path traversal in its Admin API log-download endpoint (GET /v1/admin/logs/file). The path confinement check uses str.startswith() rather than proper boundary validation, allowing an authenticated admin to read .log, .jsonl, and .json files outside the configured LOG_FOLDER.
- CVE-2026-11918Medium
IBM ContextForge MCP Gateway <= v1.0.4 allows an authenticated user to bypass protection mechanisms due to incomplete recursive inspection of nested payload content. The flaw enables evasion of security controls through content hidden in nested structures.
- CVE-2026-18489High
IBM ContextForge MCP Gateway - Translate utility <= 1.0.8 MCP Context Forge could allow a remote attacker to obtain sensitive information from other sessions due to exposure of data elements to the wrong session.
- CVE-2026-18486High
IBM ContextForge MCP Gateway <= v1.0.7 MCP Context Forge could allow a remote authenticated attacker to obtain sensitive credentials and escalate privileges due to improper validation of jq filters.
- CVE-2026-77822High
IBM ContextForge MCP Gateway could allow a remote authenticated attacker to obtain sensitive information due to server-side request forgery via DNS rebinding.
Original NVD description (English source)
IBM ContextForge MCP Gateway 0.1.0 through 1.0.5 is vulnerable to a server-side request Forgery (SSRF) that allows authenticated users with gateway creation privileges to perform arbitrary HTTP POST requests to internal network resources and cloud metadata endpoints. The vulnerability occurs during OAuth-enabled gateway registration when the system fails to validate the oauth_config.token_url parameter. When registering a gateway with OAuth client credentials authentication, an attacker can supply a malicious token_url pointing to internal services, cloud metadata endpoints (AWS IMDSv1, GCP, Azure), or localhost-bound services. The application immediately performs an HTTP POST request to the attacker-controlled URL with form-encoded credentials in the body. If the response cannot be parsed as a valid OAuth token response, up to 256 characters of the response body are reflected back to the attacker in the HTTP 502 error message. This vulnerability bypasses existing SSRF protections that are applied to the gateway.url field but not to OAuth configuration parameters.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS