CVE-2026-110279: high-severity vulnerability in IBM ContextForge MCP Gateway
IBM ContextForge MCP Gateway is affected by an improper authentication vulnerability
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.1epss 0.4%
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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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-18484MEDIUMIBM ContextForge MCP Gateway is affected by a denial-of-service via tool name collision through slug normalizationEPSS 0.5%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-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%