CVE-2026-18484

A gateway name collision could make a team’s public MCP tool unavailable

IBM · ContextForge MCP Gateway federated tool registry

First documented disclosure · Review checkpoint

Summary

A team member authorized to register gateways could cause calls to an existing tool to fail for the whole team.

Severity and exploitation evidence

Medium · 6.5/10 · CVSS 3.1. Severity source.

Exploitation not established: The reviewed public disclosures do not report exploitation in the wild.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

Normalization could give a newly registered tool the same effective name as an existing team tool. The gateway then could not resolve calls to one tool.

Conditions required

A user is authenticated and can create gateways in the affected team. A public tool with a conflicting normalized name already exists.

Potential impact

The affected tool could be unavailable to team members until an administrator resolves the collision.

Affected versions and configurations

1.0.0 through 1.0.11.

Fix and mitigation status

1.1.0.

Practical next steps

Upgrade to 1.1.0. If a collision already affects a team, have an administrator resolve the conflicting registration.

Operating lesson

Enforce uniqueness on normalized names at registration time within each team.

Evidence and limits

IBM’s October 27 disclosure bounds the impact to availability of the conflicting tool.

Sources