IBM CONTEXTFORGE MCP GATEWAY · CVE-2026-94407 · AI agents & MCP
FIX → 1.1.0 ✓ verified
IBM ContextForge MCP Gateway 1.0.0 through 1.0.11 validates tool arguments against a JSON Schema pattern supplied at tool registration, and a crafted catastrophic-backtracking regex can make that validation consume unbounded CPU. An authenticated user with tool-registration privileges can therefore degrade or take down gateway availability.
first public Nov 13, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams self-hosting IBM ContextForge MCP Gateway v1.0.0 through v1.0.11. The gateway validates tool arguments, tool results and prompt arguments against JSON Schemas supplied by tool and prompt authors or federated remote MCP servers, and an unbounded regex in a pattern field can exhaust CPU on a gateway worker. An authenticated user with tool-registration privileges is needed; deployments where only trusted admins register tools and that connect no untrusted remote servers carry less risk.
Not affected if no-tool-registration-by-users, version-outside-range
Who cares ibm-contextforge, mcp, self-hosted
IBM ContextForge MCP Gateway 1.0.0 through 1.0.11 is potentially vulnerable to denial of service due to uncontrolled regular expression complexity (CWE-400 / ReDoS). An authenticated user with tool-registration privileges can embed catastrophically backtracking regex patterns in a tool's JSON Schema pattern field; when ContextForge validates arguments against that schema, the validation call may consume unbounded CPU, potentially degrading gateway availability.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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.
Upgrade to 1.1.0
v1.1.0