Public vulnerability disclosure

CVE-2026-110194

IBM ContextForge MCP Gateway is affected by a server-side request forgery vulnerability

publishedCWE-918

IBM ContextForge MCP Gateway 1.0.0 through 1.0.11 is vulnerable to server-side request forgery (SSRF). This may allow an authenticated attacker to send unauthorized requests from the system, potentially leading to network enumeration or facilitating other attacks.

Technical severity5.4 mediumCVSS 3.1 · CNA: ibm
Published2026-11-13Source updated 2026-11-13
Collected2026-11-131 attributed source

Fixes and workarounds

Fix

Product(s)Version(s) number and/or range Remediation/Fix/InstructionsIBM ContextForge MCP Gatewayv1.1.0Install or upgrade to v1.1.0 [ v1.1.0 Release Notes https://github.com/IBM/mcp-context-forge/releases/tag/v1.1.0 ]

Source: CNA: ibm

Workaround

IBM strongly recommends upgrading to the fixed version. If this is not possible restrict the accepted authorization server issuers by setting `DCR_ALLOWED_ISSUERS` to a list of trusted issuers, or disable Dynamic Client Registration (`DCR_ENABLED=false`), and restrict gateway creation permissions to trusted users.

Source: CNA: ibm

Fix

The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.

Source: CNA: ibm

Affected products and versions

Affected products, source version ranges and reporting authorities
ProductVersionsAuthority
ContextForge MCP Gateway
IBM
≥ 1.0.0; ≤ 1.0.11 (affected, semver) CNA: ibm

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

CVSS scores, vectors and reporting authorities
Version / scoreVectorAuthority
3.1 / 5.4
medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:NCNA: ibm

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide