CVE-2026-110195: medium-severity vulnerability in IBM ContextForge MCP Gateway
IBM ContextForge MCP Gateway is affected by an authorization bypass vulnerability
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 5.4epss 0.2%
IBM ContextForge MCP Gateway 1.0.0 through 1.0.11 could allow an authenticated caller to bypass upstream credential-level authorization policies due to an insufficiently specific cache key in the RFC 8693 token exchange cache, enabling reuse of cached upstream bearer tokens across different credentials belonging to the same user.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Affected products
IBM · ContextForge MCP GatewayRelated CVEs — IBM ContextForge MCP Gateway
In the same product, most dangerous first.
CVE-2026-18486HIGHIBM ContextForge MCP Gateway is affected by credential disclosure and privilege escalation via jq filter executionEPSS 0.6%CVE-2026-78573CRITICALIBM ContextForge MCP Gateway is affected by use of default credentialsEPSS 0.6%CVE-2026-110189MEDIUMIBM ContextForge MCP Gateway is affected by a denial of service due to an incomplete list of disallowed jq inputsEPSS 0.5%CVE-2026-18484MEDIUMIBM ContextForge MCP Gateway is affected by a denial-of-service via tool name collision through slug normalizationEPSS 0.4%CVE-2026-77822HIGHIBM ContextForge MCP Gateway is affected by server-side request forgery (DNS rebinding) via the A2A agent invocation endpointEPSS 0.4%CVE-2026-110178MEDIUMIBM ContextForge MCP Gateway is affected by an improper access control vulnerability in configuration importEPSS 0.4%