---
id: "CVE-2026-18484"
page: "https://infrastack.ai/live/CVE-2026-18484"
kind: "vulnerability"
aliases: ["CVE-2026-18484"]
title: "IBM ContextForge MCP Gateway: slug collisions let an authenticated user cause denial of service"
severity: "medium"
cvss: 6.5
epss: null
exploited: false
status: "open"
category: "ai-tooling"
products: [{"name": "ContextForge MCP Gateway", "fixed": ["1.1.0"], "affected": ">= 1.0.0, <= 1.0.11", "ecosystem": "vendor"}]
ecosystems: ["vendor"]
tags: ["ai-tooling", "ibm-contextforge", "mcp", "self-hosted"]
not_affected_if: ["auth-required", "no-authenticated-users", "unaffected-version"]
published_at: "2026-11-08T18:17:04+00:00"
first_seen_at: "2026-11-08T18:22:22+00:00"
updated_at: "2026-11-08T18:23:25+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-18484", "first_seen_at": "2026-11-08T18:22:22+00:00"}, {"source": "analyst", "url": "https://www.ibm.com/support/pages/security-bulletin-ibm-contextforge-mcp-gateway-affected-denial-service-tool-name-collision-through-slug-normalization", "first_seen_at": "2026-11-08T18:23:25+00:00", "cites": ["https://www.ibm.com/support/pages/security-bulletin-ibm-contextforge-mcp-gateway-affected-denial-service-tool-name-collision-through-slug-normalization"]}]
exploit_sources: []
---

# IBM ContextForge MCP Gateway: slug collisions let an authenticated user cause denial of service

Link for people: https://infrastack.ai/live/CVE-2026-18484 (this .md is for agents)

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.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- vendor:ContextForge MCP Gateway affected >= 1.0.0, <= 1.0.11 fixed 1.1.0

## How to check

Check the installed ContextForge MCP Gateway version; 1.0.0 through 1.0.11 is affected. A tools/call failing with an ambiguity error for one tool suggests an active slug collision between two gateway registrations in the same team. Workaround if you cannot upgrade: an admin renames or removes one of the two conflicting gateway registrations. No setting prevents the collision before v1.1.0 (IBM).

## Fix

Upgrade IBM ContextForge MCP Gateway to v1.1.0

## Timeline

- 2026-11-08T18:22:22+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-18484
- 2026-11-08T18:23:25+00:00 analyst https://www.ibm.com/support/pages/security-bulletin-ibm-contextforge-mcp-gateway-affected-denial-service-tool-name-collision-through-slug-normalization — IBM bulletin (27 Oct 2026) read: affected 1.0.0-1.0.11, fixed in v1.1.0; workaround is admin renaming/removing a conflicting gateway; no config prevents it. No exploitation or PoC seen; social not searched.

## Documents

- [advisory] IBM Security Bulletin: ContextForge MCP Gateway DoS via slug normalization https://www.ibm.com/support/pages/security-bulletin-ibm-contextforge-mcp-gateway-affected-denial-service-tool-name-collision-through-slug-normalization

## From the sources

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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_