CVE-2026-110279

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.

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

• 8.1CVSS 3.1, Highfrom the CNA (ibm)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

What to do

• 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 ]CNA solution statement
• 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.CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

Timeline

1. 13 Nov 2026 Published

Weakness

• CWE-287

References

• www.ibm.comvendor-advisorypatch