CVE-2026-110279
IBM ContextForge MCP Gateway is affected by an improper authentication vulnerability
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.
Fixes and workarounds
Fix
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 ]
Source: CNA: ibmWorkaround
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.
Source: CNA: ibmFix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: ibmAffected products and versions
| Product | Versions | Authority |
|---|---|---|
| ContextForge MCP Gateway IBM |
≥ 1.0.0; ≤ 1.1.0 (affected, semver) | CNA: ibm |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 3.1 / 8.1 high |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N | CNA: ibm |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://www.ibm.com/support/pages/node/7296490CNA: ibm · vendor-advisory, patch
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.