CVE-2026-18484
IBM ContextForge MCP Gateway is affected by a denial-of-service via tool name collision through slug normalization
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.
Fixes and workarounds
Fix
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 ]
Source: CNA: ibmWorkaround
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.
Source: CNA: ibmFix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: ibmAffected products and versions
| Product | Versions | Authority |
|---|---|---|
| ContextForge MCP Gateway IBM |
≥ 1.0.0; ≤ 1.0.11 (affected, semver) | CNA: ibm |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 3.1 / 6.5 medium |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H | CNA: ibm |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://www.ibm.com/support/pages/node/7294233CNA: ibm · vendor-advisory, patch
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.