IBM ContextForge MCP Gateway is affected by server-side request forgery (DNS rebinding) via the A2A agent invocation endpoint
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.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Ibm | Contextforge Mcp Gateway |
|
Vendor Solution
IBM strongly recommends addressing the vulnerability now. Product(s)Version(s) number and/or range Remediation/Fix/InstructionsIBM ContextForge MCP Gateway<= v1.0.8Upgrade to v1.0.9 https://github.com/IBM/mcp-context-forge/releases/tag/v1.0.9 Note: <Component A / B names> are bundled with <Product profile name> to provide <feature / function description>
Vendor Workaround
Operators who cannot immediately upgrade can reduce exposure by: 1. **Disable A2A** — set the environment variable `MCPGATEWAY_A2A_ENABLED=False` to disable the A2A subsystem entirely. This removes the vulnerable endpoint from the attack surface at the cost of A2A functionality. 2. **Restrict A2A create/invoke permissions** — revoke A2A creation and invocation rights from developer and team_admin roles in environments where A2A is not required. 3. **Network-level egress controls** — enforce outbound network policy at the host or cloud level to block the gateway process from reaching cloud metadata endpoints and private RFC 1918 address ranges, preventing exploitation of the DNS-rebinding window even if a rebind attempt succeeds. None of these mitigations eliminate the underlying vulnerability; IBM strongly recommends upgrading to the fixed version.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.370% probability within 30 days)
| Link | Providers |
|---|---|
| https://www.ibm.com/support/pages/node/7286055 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Ibm contextforge
|
|
| CPEs | cpe:2.3:a:ibm:contextforge:*:*:*:*:*:python:*:* | |
| Vendors & Products |
Ibm contextforge
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Ibm contextforge Mcp Gateway
|
|
| Vendors & Products |
Ibm contextforge Mcp Gateway
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | IBM ContextForge MCP Gateway could allow a remote authenticated attacker to obtain sensitive information due to server-side request forgery via DNS rebinding. | |
| Title | IBM ContextForge MCP Gateway is affected by server-side request forgery (DNS rebinding) via the A2A agent invocation endpoint | |
| First Time appeared |
Ibm
Ibm contextforge-mcp-gateway |
|
| Weaknesses | CWE-918 | |
| CPEs | cpe:2.3:a:ibm:contextforge-mcp-gateway:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Ibm
Ibm contextforge-mcp-gateway |
|
| References |
| |
| Metrics |
cvssV3_1
|