CONTEXTFORGE MCP GATEWAY · CVE-2026-18484 · AI agents & MCP
FIX → 1.1.0 ✓ verified
In ContextForge MCP Gateway 1.0.0 to 1.0.11, a user with gateway-create permission can register a gateway whose computed tool slug collides with an existing public tool in the same team. Calls to that tool then fail with an ambiguity error for every team member until an admin intervenes. IBM rates it CVSS 6.5 and fixes it in v1.1.0.
first public Nov 8, 2026 · 2 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Teams running a self-hosted ContextForge MCP Gateway 1.0.0 to 1.0.11 where more than one user can register federated gateways. The attacker needs a valid account with gateway-create permission, and the effect is availability only: one tool becomes unusable for the team. Setups where only trusted admins can create gateways carry little risk.
Not affected if auth-required, no-authenticated-users, unaffected-version
Who cares ibm-contextforge, mcp, self-hosted
1.0.0 through 1.0.11 is affectedv1.1.0 (IBM)IBM ContextForge MCP Gateway 1.0.0 through 1.0.11 could allow a remote authenticated attacker to cause a denial of service due to improper slug normalization causing tool name collisions.
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?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
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.
Upgrade to 1.1.0
Upgrade IBM ContextForge MCP Gateway to v1.1.0