IBM ContextForge MCP Gateway 1.0.0 through 1.0.11 could allow a remote authenticated attacker to cause a denial of
Source GCVE Database
Not known to be exploited · CVSS 6.5 Medium.
Data as of 8 Nov 2026, 20:47 UTC
Thin evidence
One scorer or none| CNA (ibm) | CVSS 3.1 | 6.5 |
|---|
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 8 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| IBMContextForge MCP Gateway | Affected
| Fixed in– |
AI-suggested
Until an official fix is available, monitor for vendor updates and consider restricting authenticated user privileges to limit potential exploitation.
Description
IBM ContextForge MCP Gateway versions 1.0.0 through 1.0.11 contain a vulnerability where improper slug normalization can cause tool name collisions. This flaw allows a remote authenticated attacker to trigger a denial of service condition. The vulnerability does not impact confidentiality or integrity but affects availability.