Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-56104 – Session Hijacking – Chainlit before 2.10.1

Be the first to know when new zero-days emerge:

Summary

CVE-2026-56104 is a critical session hijacking vulnerability in Chainlit, the open-source Python framework for building and deploying AI/LLM chatbot applications, affecting all versions before 2.10.1. An unauthenticated remote attacker who obtains a valid session ID can exploit the restore_existing_session WebSocket path to assume a victim user’s authenticated session without any ownership verification. With a CVSS v4.0 score of 9.1 (Critical) and a CVSS v3.1 score of 7.4 (High), this vulnerability poses a severe risk to any internet-exposed Chainlit deployment.

Technical details

  • Root cause: The restore_existing_session WebSocket handler in Chainlit did not verify that the requesting party owned the session being restored. The flaw is classified as CWE-862 (Missing Authorization) — specifically, the absence of a session ownership check during WebSocket reconnection.
  • Trigger conditions: An attacker must possess a valid sessionId belonging to an authenticated user. Session IDs can be obtained through network interception, application-layer leakage, or other means.
  • Attack vector: Network-reachable via WebSocket; no authentication or user interaction is required to attempt exploitation. Attack complexity is rated High (AC:H), reflecting the requirement to obtain a valid session ID.
  • Impact: Successful exploitation allows the attacker to fully assume the victim’s identity — inheriting their roles, permissions, access to restricted data, and the ability to invoke AI tools on the victim’s behalf. Confidentiality and integrity impact are both rated High (VC:H/VI:H); availability is not affected.

Affected software

  • Chainlit — all versions from the earliest release up to and including the version immediately prior to 2.10.1
    • Concretely: all chainlit PyPI releases before 2.10.1

Severity

  • CVSS v3.1 Base Score: 7.4 (HIGH)
  • CVSS v3.1 Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
  • CVSS v4.0 Base Score: 9.1 (CRITICAL)
  • CVSS v4.0 Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate — Upgrade: Update Chainlit to version 2.10.1 or later. This release adds a _session_owner_matches_user ownership check to the restore_existing_session function; attempts to restore a session by a non-owning user are now rejected with a ConnectionRefusedError("authorization failed") (PR #2857).
  • If immediate patching is not possible:
    • Restrict public network access to Chainlit’s WebSocket endpoint via firewall rules or reverse proxy configuration, limiting access to trusted networks or authenticated users only.
    • Monitor WebSocket connection logs for unexpected restore_existing_session events originating from IP addresses or users that do not match the original session context.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge