CVE-2026-18484 PUBLISHED

IBM ContextForge MCP Gateway is affected by a denial-of-service via tool name collision through slug normalization

Assigner: ibm
Reserved: 31.07.2026 Published: 08.11.2026 Updated: 08.11.2026

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.

Metrics

CVSS 3.1

CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CVSS Score: 6.5

Attack Vector	Network	Scope	Unchanged
Attack Complexity	Low	Confidentiality Impact	None
Privileges Required	Low	Integrity Impact	None
User Interaction	None	Availability Impact	High

CVSS 3.1

Product Status

Vendor	IBM
Product	ContextForge MCP Gateway
Versions	affected from 1.0.0 to 1.0.11 (incl.)

Workarounds

If an immediate upgrade is not possible, an administrator can mitigate an active collision by renaming or removing one of the two conflicting gateway registrations, which restores invocability of the affected tool. There is no configuration setting that prevents the collision from being created prior to the v1.1.0 fix.

IBM strongly recommends upgrading to v1.1.0.

Solutions

IBM strongly recommends addressing the vulnerability now.

Product(s)Version(s) number and/or range Remediation/Fix/InstructionsIBM ContextForge MCP Gateway

1.0.0 - v1.0.11Upgrade to v1.1.0. See [ v1.1.0 release notes https://github.com/IBM/mcp-context-forge/releases/tag/v1.1.0 ]

References

https://www.ibm.com/support/pages/node/7294233

Problem Types

CWE-706 Use of Incorrectly-Resolved Name or Reference CWE