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.
Published: 2026-11-08
Score: 6.5 Medium
EPSS: n/a
KEV: No
Impact: Denial of Service
Action: Immediate Patch
AI Analysis

Impact

IBM ContextForge MCP Gateway 1.0.0 through 1.0.11 contains a flaw in slug normalization that allows a remote authenticated attacker to cause a denial of service by creating tool name collisions. The collision prevents the affected tool from being invoked, disrupting the gateway’s availability. This weakness is identified as CWE-706, representing improper handling of identifiers or naming conflicts.

Affected Systems

The vulnerability affects IBM ContextForge MCP Gateway versions 1.0.0 through 1.0.11. The vendor recommends upgrading to version 1.1.0, which removes the slug normalization issue. Earlier releases do not contain the fix.

Risk and Exploitability

The CVSS score is 6.5, indicating a moderate severity. EPSS is not available, so the exploitation probability is unknown, and the vulnerability is not listed in CISA’s KEV catalog. The attack requires remote authentication, meaning an attacker must have valid credentials to register the colliding gateway. Once a collision occurs, denial of service follows immediately, affecting all operations that rely on the compromised tool.

Generated by OpenCVE AI on November 8, 2026 at 19:53 UTC.

Remediation

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.

OpenCVE Recommended Actions

  • Upgrade IBM ContextForge MCP Gateway to version 1.1.0.
  • If an upgrade is not immediately possible, rename or remove one of the two conflicting gateway registrations to restore functionality of the affected tool.
  • Enable application logging for slug collision incidents and configure alerts to notify administrators when collisions occur, allowing timely detection and resolution.

Generated by OpenCVE AI on November 8, 2026 at 19:53 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

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

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

Subscriptions

Ibm Contextforge Mcp Gateway
cve-icon MITRE

Status: PUBLISHED

Assigner: ibm

Published:

Updated: 2026-11-08T17:54:59.348Z

Reserved: 2026-07-31T13:22:47.530Z

Link: CVE-2026-18484

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-11-08T18:17:04.010

Modified: 2026-11-08T18:17:04.123

Link: CVE-2026-18484

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-11-08T20:00:15Z

Weaknesses
  • CWE-706

    Use of Incorrectly-Resolved Name or Reference