CVE-2026-8355Medium· 5.4▾ SunlitIBM 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…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 29.7 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the CISA ADP record, not NVD.
Exploit-prediction probability, daily snapshots since Oct 20.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.2%
— → 5.4
none → medium
0.2% → 0.2%
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.
contextforge_mcp_gateway >= 0.1.0 <= 1.0.5IBM strongly recommends addressing the vulnerability now.
Product(s)Version(s) number and/or range Remediation/Fix/InstructionsIBM ContextForge MCP Gateway
2.0>=v1.0.6Upgrade to v1.0.6 or later. See release notes: https://github.com/IBM/mcp-context-forge/releases/tag/v1.0.6 https://github.com/IBM/mcp-context-forge/releases/tag/v1.0.6%29
If an immediate upgrade to v1.0.6 is not possible, restrict access to the gateway registration API:
Remove the gateways.create permission from the developer role or any role assigned to untrusted users.
Enforce network-level egress controls (firewall / security group rules) to block outbound HTTP/HTTPS from the gateway host to cloud metadata addresses (169.254.254.169/32, fd00:ec2::254/128), RFC 1918 ranges, and loopback (127.0.0.0/8).
IBM strongly recommends upgrading to the fixed version as soon as possible.
Field changes observed since this record was first indexed.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-11918Medium· 5.4IBM ContextForge MCP Gateway <= v1.0.4 IBM mcp-context-forge could allow an authenticated user to bypass protection mechanisms due to incomplete recursive inspection of nested payload content.
CVE-2025-12832Medium· 4.6IBM InfoSphere Information Server 11.7.0.0 through 11.7.1.6 is vulnerable to server-side request forgery (SSRF)
CVE-2025-36324Medium· 4.3IBM watsonx.data intelligence 5.2.0, 5.2.1, 5.2.2, 5.3.0 s vulnerable to server-side request forgery (SSRF)
CVE-2025-36085Medium· 5.4IBM Concert 1.0.0 through 2.0.0 Software is vulnerable to server-side request forgery (SSRF)
CVE-2026-94402Medium· 6.1IBM vulnerable to cross-site scripting (XSS) via unsanitized title truncation
CVE-2026-93888High· 7.8IBM Sterling Connect:Direct for Unix Buffer Overflow