
CVE-2026-110279 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 … https://www.cve.org/CVERecord?id=CVE-2026-110279
Signal is active with 1 mentions in latest observed window
Recommended action window: Monitor and triage in normal cycle
NVD 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.
Priority
LOW
Exploitation
NONE
PoC
NONE
Patch
NONE
Momentum
STABLE
If you run products in this scope, you should treat this CVE as relevant to your environment.

CVE-2026-110279 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 … https://www.cve.org/CVERecord?id=CVE-2026-110279

🚨 IBM's ContextForge MCP Gateway mishandles credentials in every release from 1.0.0 through 1.1.0. If you run ContextForge MCP Gateway anywhere in your stack, check which version you have deployed: 1.0.0 through 1.1.0 is the affected range for CVE-2026-110279. First public Nov 13 https://infrastack.ai/live/CVE-2026-110279?u=1794609214&utm_source=x&utm_medium=social&utm_content=437

@grok Has IBM released a fix or workaround for CVE-2026-110279 in ContextForge MCP Gateway 1.0.0 to 1.1.0, and what should teams check first?

MCP gateway ไม่ใช่แค่ทางผ่าน แต่ถือ credential ไว้ด้วย 🛡️ IBM แก้ CVE-2026-110279 (CVSS 8.1) ใน ContextForge 1.0.0–1.1.0 ผู้ใช้ที่ล็อกอินแล้วส่ง header X-Upstream-Authorization แทน credential ของ gateway ได้ ข้ามสิทธิ์และ audit อัปเป็น 1.1.1 หรือตัด header นี้ที่ proxy ครับ https://t.co/81JknE097C

Your MCP gateway holds the upstream OAuth tokens. What stops a client sending its own? In IBM ContextForge up to 1.1.0, nothing. X-Upstream-Authorization got renamed to Authorization upstream, so a logged-in user could swap the credential (CVE-2026-110279, 8.1). Fixed in 1.1.1.

#NØØT_Security_Alerts 🚨 #ALERT — #NEW #IBMContextForge #HighSeverityCredentialOverride: Authenticated MCP Users Can Override Upstream Credentials November 12, 2026 — IBM security disclosure CVE-2026-110279 (CVSS v3.1: 8.1) affects IBM ContextForge MCP Gateway 1.0.0–1.1.0. An authenticated caller can use the X-Upstream-Authorization header to replace gateway-managed OAuth, bearer or basic credentials, potentially bypassing per-user permissions and audit attribution. Upgrade to v1.1.1 after compatibility testing and verify deployed instances. Until then, strip this header at the ingress proxy and restrict MCP access. IBM’s advisory does not establish real-world exploitation. https://www.ibm.com/support/pages/node/7296490 https://github.com/IBM/mcp-context-forge/releases/tag/v1.1.1 #MCPSecurity #AuthenticationBypass #AccessControl
1 of 1 entries
| Part | Vendor | Product | Version | Target SW | Target HW |
|---|---|---|---|---|---|
| App | ibm | contextforge | - | python | - |