IBM ContextForge MCP Gateway is affected by an improper authentication vulnerability

published 2026-11-13 9h ago modified 2026-11-13 9h ago also EUVD-2026-125807

cvss: 8.1; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: —; no EPSS score yet
public exploits: 0; none known

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.

Patch / fix

links 1

ibm.com/support/pages/node/7296490 advisory

Is CVE-2026-110279 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by	version	score	vector
CNA	3.1	8.1	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
NVD	3.1	8.1	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Affected products

IBM ContextForge MCP Gateway

Classification

Weakness

CWE-287 Improper Authentication

References

ibm.com /support/pages/node/7296490
vendor-advisory, patch

Sources

CVE List CVE-2026-110279
NVD CVE-2026-110279

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.