Authenticated thread access via unchecked threadId
Published Jan 14, 2026 · Updated Jan 14, 2026
Authorization bypass in Chainlit before 2.8.5 allows remote authenticated users to view other users' threads or take ownership. The WebSocket connect handler accepts a client-supplied threadId and resumes that thread without comparing its stored author to the authenticated user's identifier. A valid login and a usable thread identifier are required; exploitation exposes another user's conversation and permits reassignment of its ownership.
Summary
What happened
Authorization bypass in Chainlit before 2.8.5 allows remote authenticated users to view other users' threads or take ownership. The WebSocket connect handler accepts a client-supplied threadId and resumes that thread without comparing its stored author to the authenticated user's identifier. A valid login and a usable thread identifier are required; exploitation exposes another user's conversation and permits reassignment of its ownership.
The record
- CVE
- CVE-2025-68492
- Published
- Jan 14, 2026
- Updated
- Jan 14, 2026
- Vendor
- Chainlit
- Product
- Chainlit
- Classifications
- CWE-639, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 14, 2026CVE publishedPublication date reported by the CVE source.
- Jan 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=prior to 2.8.5
What conditions does exploitation require?
What is affected?
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