Cross-user MCP context access via cache collision
Published Sep 14, 2026 · Updated Sep 14, 2026
Improper cache isolation in IBM Langflow OSS 1.0.0 through 1.11.5 allows remote authenticated users to access another user's MCP context. The MCP Tools component keys a shared process-local cache only by server display name, omitting the user, session, flow, and resolved configuration. Exploitation requires caching, matching server names, and both users landing on the same backend worker; reuse can expose data or permit actions through the first user's MCP context.
Summary
What happened
Improper cache isolation in IBM Langflow OSS 1.0.0 through 1.11.5 allows remote authenticated users to access another user's MCP context. The MCP Tools component keys a shared process-local cache only by server display name, omitting the user, session, flow, and resolved configuration. Exploitation requires caching, matching server names, and both users landing on the same backend worker; reuse can expose data or permit actions through the first user's MCP context.
The record
- CVE
- CVE-2026-12763
- Published
- Sep 14, 2026
- Updated
- Sep 14, 2026
- Vendor
- IBM
- Product
- Langflow OSS
- Classifications
- CWE-306, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 14, 2026CVE publishedPublication date reported by the CVE source.
- Sep 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0.0 <=1.11.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo