Loading vulnerability…
CVE-2026-56104 is a session hijacking vulnerability in Chainlit versions earlier than 2.10.1. The WebSocket session-restoration flow accepts a supplied session identifier through the restore_existing_session path but does not verify that the requester owns the referenced session. An unauthenticated remote attacker who presents a valid identifier for an authenticated user's restorable session can restore and inherit that user's session context.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A session-hijacking flaw in Chainlit prior to version 2.10.1. An unauthenticated attacker possessing a valid sessionId can use the WebSocket session-restoration path to inherit the victim's authenticated session, including their permissions and roles, enabling unauthorized tool invocation and access to victim-restricted data.
A session hijacking vulnerability in Chainlit before 2.10.1 that allows unauthenticated attackers to restore and inherit authenticated user sessions via WebSocket session restoration without ownership verification.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.