IBM ContextForge MCP Gateway is affected by a server-side request forgery vulnerability
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| IBM | ContextForge MCP Gateway | affected |
|
No data.
No data.
No data available yet.
Vendor Solution
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 ]
Vendor 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.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Link | Providers |
|---|---|
| https://www.ibm.com/support/pages/node/7296696 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | IBM ContextForge MCP Gateway is affected by a server-side request forgery vulnerability | |
| First Time appeared |
Ibm
Ibm contextforge Mcp Gateway |
|
| Weaknesses | CWE-918 | |
| CPEs | cpe:2.3:a:ibm:contextforge_mcp_gateway:1.0.0:*:*:*:*:*:*:* cpe:2.3:a:ibm:contextforge_mcp_gateway:1.0.11:*:*:*:*:*:*:* |
|
| Vendors & Products |
Ibm
Ibm contextforge Mcp Gateway |
|
| References |
| |
| Metrics |
cvssV3_1
|