PoC Monitor
← All CVEs
CVE-2026-110279published 13 Nov 2026 21:43 UTCData: JSON · API

IBM ContextForge MCP Gateway

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub · +1 suspicious, not counted
CVSS8.1high · scored by CNA · CWE-287
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

IBM ContextForge MCP Gateway
  • >= 1.0.0, <= 1.1.0

Mitigation

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 ]

Workaround

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.

References

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published13 Nov 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

1 suspicious or fake

Suspicious or fake 1
RepositoryCreatedStarsAssessment
webpro255/awesome-ai-agent-attacks 7 Apr 2026 −220 d 91 Suspicious · score 80
Why suspicious
  • references an exfiltration/paste endpoint in README.md
  • references an exfiltration/paste endpoint in TAXONOMY.md
  • stars without code

Only PoCs count toward the first-PoC date and the characteristics below. Suspicious repositories (score ≥ 50) never count. Do not run PoC code from unknown sources.