IBM CONTEXTFORGE MCP GATEWAY · CVE-2026-110279 · AI agents & MCP
FIX → 1.1.1 ✓ verified
IBM ContextForge MCP Gateway versions 1.0.0 through 1.1.0 let the X-Upstream-Authorization request header replace the gateway-managed credential used for upstream calls. An authenticated user can make upstream requests under a different credential, bypassing per-user permissions and audit attribution.
first public Nov 13, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams self-hosting IBM ContextForge MCP Gateway 1.0.0 to 1.1.0 with gateway-managed upstream credentials (OAuth authorization_code or client_credentials, bearer, basic, or custom auth headers) are exposed. Any authenticated user can send an X-Upstream-Authorization header that replaces the stored credential, so requests run under another credential, bypassing per-user permissions and audit attribution. Deployments with no gateway-managed upstream auth, or already on 1.1.1, can skip it.
Not affected if no-upstream-auth-configured, outside-affected-range
Who cares ibm-contextforge, mcp, self-hosted
Upgrade to 1.1.1
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.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
v1.1.1 (fix PR IBM/mcp-context-forge#7341)