IBM CONTEXTFORGE MCP GATEWAY · CVE-2026-110195 · AI agents & MCP
FIX → 1.1.0 ✓ verified
IBM ContextForge MCP Gateway versions 1.0.0 through 1.0.11 cache upstream bearer tokens from RFC 8693 token exchange under a key that is not specific enough. An authenticated user can reuse a cached token across different credentials they hold, bypassing upstream credential-level authorization policies.
first public Nov 13, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams running IBM ContextForge MCP Gateway v1.0.0 to v1.0.11 with OAuth token exchange that uses the caller's inbound JWT. The token cache is keyed by gateway, user account and audience, not the specific JWT, so a restricted credential (such as an API token) can reuse an upstream bearer token cached by a higher-privileged credential (such as a session token) of the same account. Teams not using token exchange, or with identical upstream permissions for all credential types, can skip it.
Not affected if identical-credential-permissions, no-token-exchange, version-outside-range
Who cares ibm-contextforge, mcp, self-hosted, token-exchange
IBM ContextForge MCP Gateway 1.0.0 through 1.0.11 could allow an authenticated caller to bypass upstream credential-level authorization policies due to an insufficiently specific cache key in the RFC 8693 token exchange cache, enabling reuse of cached upstream bearer tokens across different credentials belonging to the same user.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
Upgrade to 1.1.0
v1.1.0 or later