Arbitrary File Read in Chainlit /project/element update flow (pre-2.9.4)
Chainlit versions prior to 2.9.4 contain an arbitrary file read issue in the /project/element element-update flow. An authenticated client can submit a crafted custom Element whose path property is attacker-controlled. Due to insufficient validation of this path, the server will copy the referenced file into the attacker’s session context and return an element identifier (chainlitKey). The attacker can then retrieve the copied file contents via the /project/file/<chainlitKey> endpoint, disclosing any file readable by the Chainlit service account (e.g., configuration, source code, environment variable files such as /proc/self/environ, and local databases such as chainlit/.langchain.db in certain deployments).
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
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.
Recent activity
23 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Unknown
Chainlit vulnerability enabling leakage of cloud environment API keys and theft of sensitive files, triggerable without user interaction.
A critical arbitrary file read vulnerability in Chainlit that allows attackers to read server-accessible files (including environment variables and database files), enabling theft of cloud/API credentials and cross-tenant data exposure in some deployments.
Arbitrary file read in Chainlit via the /project/element endpoint by abusing a custom element’s controlled 'path' field, enabling attackers to read any file accessible to the Chainlit server (e.g., API keys, credentials, source code, configs, databases, auth secrets).
The version that knows your environment.
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.