Evidence · DiggingBeagle record
IBM bulletin: ContextForge token-exchange cache authorization bypass
IBM vendor advisory on RFC 8693 exchanged-token cache incorrectly shared between distinct credentials for the same user.
- Published
- Nov 13, 2026
- Source role
- vendor statement
Evidence record
IBM vendor advisory on RFC 8693 exchanged-token cache incorrectly shared between distinct credentials for the same user.
Claim-level citations (2)
- supportsContextForge reused an exchanged upstream bearer token between credentials with different permissions for the same user: ContextForge can exchange the incoming caller JWT for a delegated MCP access token and cache that token. A vulnerable cache key bound the entry to the gateway, user account and upstream audience, but not the specific inbound credential or its effective scope. If a user first used a privileged interactive session and then a more limited API token, the latter could receive an upstream access token cached for the former, crossing credential-level authorization even though both belonged to the same human account.
IBM Security Bulletin CVE-2026-110195, Summary, affected versions and token-exchange cache correction
- supportsContextForge reused an exchanged upstream bearer token between credentials with different permissions for the same user: IBM identifies CVE-2026-110195 as affecting v1.0.0 through v1.0.11 and fixed by 1.1.0; it does not identify field exploitation or a cross-user data breach. The mismatch requires differently privileged same-user credentials and enabled inbound-JWT token exchange. The issue is distinct from caller header override and per-server identity propagation: it is a cache identity binding failure.
Primary disclosure: results, scope and limitations