# CVE-2026-18484: IBM ContextForge MCP Gateway is affected by a denial-of-service via tool name collision through slug normalization

Status: published. Published: 2026-11-08. Updated: 2026-11-08.

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.

## Remediation

- 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: ibm)
- 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. (source: CNA: ibm)
- fix: The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches. (source: CNA: ibm) — https://www.ibm.com/support/pages/node/7294233

## Affected products and versions

- IBM / ContextForge MCP Gateway: ≥ 1.0.0; ≤ 1.0.11 (affected, semver). Source: CNA: ibm

## Severity and prioritization

- CVSS 3.1: 6.5 (medium); CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H; source: CNA: ibm

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-706

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://www.ibm.com/support/pages/node/7294233 (CNA: ibm; vendor-advisory, patch)

## Provenance

- CNA: ibm: https://www.cve.org/CVERecord?id=CVE-2026-18484; retrieved 2026-11-08; source updated 2026-11-08

Revision: 9fc44500448b82dff3cabfc749082110308848ec93619ccc9f3edd7cb675856b

Canonical: https://y2.dev/cve/CVE-2026-18484

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.