CVE-2026-110279: IBM ContextForge MCP Gateway · Improper Authentication
Affects IBM ContextForge MCP GatewaySource CVE Database V5
Not known to be exploited · CVSS 8.1 High.
Data as of 13 Nov 2026, 22:02 UTC
Thin evidence
One scorer or none| CNA (ibm) | CVSS 3.1 | 8.1 |
|---|
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 13 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 13 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| IBMContextForge MCP Gateway | Affected
| Fixed in– |
CPE configurations (2)
cpe:2.3:a:ibm:contextforge_mcp_gateway:1.0.0:*:*:*:*:*:*:*cpe:2.3:a:ibm:contextforge_mcp_gateway:1.1.0:*:*:*:*:*:*:*
Description
IBM ContextForge MCP Gateway 1.0.0 through 1.1.0 is vulnerable to improper credential handling because the X-Upstream-Authorization request header can override the gateway-managed upstream credential for OAuth (authorization_code and client_credentials), bearer and basic authenticated gateways, which could allow an authenticated user to cause upstream requests to be made with a different credential and bypass per-user permission and audit attribution.