Metrics
Affected Vendors & Products
No advisories yet.
Solution
IBM strongly recommends addressing the vulnerability now. Product(s)Version(s) number and/or range Remediation/Fix/InstructionsIBM ContextForge MCP Gateway2.0Download and deploy v1.1.1 [ Release notes v1.1.1 https://github.com/IBM/mcp-context-forge/releases/tag/v1.1.1 ]
Workaround
Remove the X-Upstream-Authorization request header at the reverse proxy or API gateway in front of IBM ContextForge MCP Gateway for all MCP endpoints, and restrict network access to MCP endpoints to trusted networks. IBM strongly recommends upgrading to the fixed version.
| Link | Providers |
|---|---|
| https://www.ibm.com/support/pages/node/7296490 |
|
Fri, 13 Nov 2026 22:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | IBM ContextForge MCP Gateway is affected by an improper authentication vulnerability | |
| First Time appeared |
Ibm
Ibm contextforge Mcp Gateway |
|
| Weaknesses | CWE-287 | |
| CPEs | cpe:2.3:a:ibm:contextforge_mcp_gateway:1.0.0:*:*:*:*:*:*:* cpe:2.3:a:ibm:contextforge_mcp_gateway:1.1.0:*:*:*:*:*:*:* |
|
| Vendors & Products |
Ibm
Ibm contextforge Mcp Gateway |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: ibm
Published:
Updated: 2026-11-13T21:43:43.544Z
Reserved: 2026-10-13T19:06:34.353Z
Link: CVE-2026-110279
No data.
Status : Awaiting Analysis
Published: 2026-11-13T22:17:21.030
Modified: 2026-11-13T22:17:21.130
Link: CVE-2026-110279
No data.
OpenCVE Enrichment
No data.