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…
Inspect the ClaimsCase · DiggingBeagle record
ContextForge 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.
Public disclosure: Nov 13, 2026
The same account presents two valid tokens whose upstream access scopes differ, in a gateway configured for token exchange and caching.
At a glance
A cached high-rights upstream bearer can be reused during a later low-rights request because cache identity does not include the exact subject credential.
Read the implicationsThe issue is distinct from caller header override and per-server identity propagation: it is a cache identity binding failure.
Limits and uncertaintyFull account
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 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.
Mechanism and trust boundary
- 01
Starting condition
The same account presents two valid tokens whose upstream access scopes differ, in a gateway configured for token exchange and caching.
Boundary: precondition and attacker capability
- 02
Trust boundary crossed or evaluated
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.
Boundary: mechanism
- 03
Observed consequence
A cached high-rights upstream bearer can be reused during a later low-rights request because cache identity does not include the exact subject credential.
Boundary: observed effect and limitations
Claims & evidence
CLM-NOV15-CF110195-MECHContextForge 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.supported
Basis: reported finding
- supportsIBM bulletin: ContextForge token-exchange cache authorization bypassvendor statement
IBM Security Bulletin CVE-2026-110195, Summary, affected versions and token-exchange cache correction
CLM-NOV15-CF110195-SCOPEIBM 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.supported
Basis: reported finding
- supportsIBM bulletin: ContextForge token-exchange cache authorization bypassvendor statement
Primary disclosure: results, scope and limitations
Implications
A cached high-rights upstream bearer can be reused during a later low-rights request because cache identity does not include the exact subject credential.
Controls and mitigations
- Upgrade to a release with credential-specific exchanged-token cache keys and drain vulnerable worker state.
- Test session JWT and API token separately under one user at different scopes, including cached-token invalidation and rollback.
Unknowns and contradictions
- The issue is distinct from caller header override and per-server identity propagation: it is a cache identity binding failure.
Sources and citation
Material revision history
- Nov 15, 2026 · Canonical change recorded · new in release · revision 250