Analysis and contextual insights are available on OpenCVE Cloud.
Vendor Solution
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 ]
Vendor Workaround
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.
Tracking
Sign in to view the affected projects.
No advisories yet.
| Link | Providers |
|---|---|
| https://www.ibm.com/support/pages/node/7294233 |
|
Sun, 08 Nov 2026 18:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | IBM ContextForge MCP Gateway is affected by a denial-of-service via tool name collision through slug normalization | |
| First Time appeared |
Ibm
Ibm contextforge Mcp Gateway |
|
| Weaknesses | CWE-706 | |
| CPEs | cpe:2.3:a:ibm:contextforge_mcp_gateway:1.0.0:*:*:*:*:*:*:* cpe:2.3:a:ibm:contextforge_mcp_gateway:1.0.11:*:*:*:*:*:*:* |
|
| Vendors & Products |
Ibm
Ibm contextforge Mcp Gateway |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: ibm
Published:
Updated: 2026-11-08T17:54:59.348Z
Reserved: 2026-07-31T13:22:47.530Z
Link: CVE-2026-18484
No data.
Status : Awaiting Analysis
Published: 2026-11-08T18:17:04.010
Modified: 2026-11-08T18:17:04.123
Link: CVE-2026-18484
No data.
OpenCVE Enrichment
No data.