CVE-2026-110194 · AI agents & MCP
NO FIX YET · SEE WHAT TO DO
IBM ContextForge MCP Gateway versions 1.0.0 through 1.0.11 contain a server-side request forgery flaw. An logged-in attacker can make the gateway send requests to hosts they choose, which can enable internal network enumeration.
first public Nov 13, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams running IBM ContextForge MCP Gateway in the 1.0.0 to 1.0.11 range are exposed. The sources say an authenticated attacker is required, so deployments where only trusted users hold accounts carry less risk. unknown whether default configurations change exposure.
Not affected if unauthenticated-access-blocked, version-above-1.0.11
Who cares ibm-contextforge, mcp, self-hosted
1.0.11; the exact fixed version is unknown from the sourcesIBM 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.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.