---
title: IBM ContextForge MCP Gateway CVE-2026-110279: any logged-in user could swap the gateway's stored upstream credential for their own via one header, bypassing per-user permissions and audit attribution | ctxsec
url: https://ctxsec.com/items/ibm-contextforge-mcp-gateway-cve-2026-110279-x-upstream-authorization-overrides-gateway-credential-fixed-1-1-1
description: "IBM says ContextForge MCP Gateway 1.0.0 through 1.1.0 always renamed a client's X-Upstream-Authorization request header to Authorization on upstream requests. That let an authenticated user override the credential the gateway manages for an upstream MCP server (stored per-user OAuth tokens, client-credentials tokens, bearer or basic auth), so upstream calls ran with a different credential, bypassing per-user permissions and audit attribution. CVSS 3.1 is 8.1. IBM's fix is v1.1.1; its workaround is to strip X-Upstream-Authorization at the reverse proxy or API gateway in front of all MCP endpoints and restrict MCP endpoints to trusted networks."
status: "official (IBM security bulletin, Nov 12, 2026; CVE record); no exploitation reported"
published: 2026-11-15
---

> IBM says ContextForge MCP Gateway 1.0.0 through 1.1.0 always renamed a client's X-Upstream-Authorization request header to Authorization on upstream requests. That let an authenticated user override the credential the gateway manages for an upstream MCP server (stored per-user OAuth tokens, client-credentials tokens, bearer or basic auth), so upstream calls ran with a different credential, bypassing per-user permissions and audit attribution. CVSS 3.1 is 8.1. IBM's fix is v1.1.1; its workaround is to strip X-Upstream-Authorization at the reverse proxy or API gateway in front of all MCP endpoints and restrict MCP endpoints to trusted networks.

[← Context & Harness Attacks](/context) · [markdown](/items/ibm-contextforge-mcp-gateway-cve-2026-110279-x-upstream-authorization-overrides-gateway-credential-fixed-1-1-1.md)

official (IBM security bulletin, Nov 12, 2026; CVE record); no exploitation reported

2026-11-15 7:38 PM ET

### IBM ContextForge MCP Gateway CVE-2026-110279: any logged-in user could swap the gateway's stored upstream credential for their own via one header, bypassing per-user permissions and audit attribution

- **Fix:** upgrade ContextForge MCP Gateway to v1.1.1.
- **Until then:** drop the `X-Upstream-Authorization` header at your reverse proxy for every MCP endpoint, and keep the gateway off untrusted networks.
- **Look back:** in proxy logs, search for client requests carrying `X-Upstream-Authorization`; legitimate clients of a gateway that holds the upstream credential should not need to send it.
- **Why it matters:** an MCP gateway's job is to hold credentials so agents and users don't; any client-controlled header that reaches upstream auth undoes that.

Sources: [IBM security bulletin: ContextForge MCP Gateway CVE-2026-110279 (Nov 12, 2026)](https://www.ibm.com/support/pages/node/7296490) · [GitHub Advisory GHSA-fp2v-98c9-h9m3 (CVE-2026-110279)](https://github.com/advisories/GHSA-fp2v-98c9-h9m3) · [IBM/mcp-context-forge fix PR #7341](https://github.com/IBM/mcp-context-forge/pull/7341)
