SSRF in Chainlit /project/element update flow (SQLAlchemy data layer)
Chainlit versions prior to 2.9.4 contain a server-side request forgery (SSRF) vulnerability in the /project/element update flow when the application is configured to use the SQLAlchemy data layer backend. An authenticated client can supply a user-controlled url value in a custom Element; during SQLAlchemy-backed element creation, Chainlit performs an outbound HTTP GET to the provided URL and stores the retrieved response via the configured storage provider. This enables an attacker to coerce the Chainlit server into making arbitrary HTTP requests to internal network services and/or cloud metadata endpoints (e.g., AWS IMDS), and to persist and later retrieve the fetched content.
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.
url values; implement outbound egress controls to block access to internal address space and sensitive link-local endpoints (notably 169.254.169.254) and to restrict outbound HTTP(S) destinations to an allowlist; add WAF/IDS rules to detect and block malicious /project/element update requests attempting to set attacker-controlled URLs.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
19 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Unknown
Chainlit SSRF vulnerability against servers hosting AI applications, triggerable without user interaction.
A high-severity SSRF vulnerability in Chainlit where insufficient URL validation in custom elements can be abused to make server-side requests to internal services and cloud metadata endpoints (notably AWS IMDS), potentially exposing IAM role credentials (especially with IMDSv1 enabled).
Server-side request forgery in Chainlit (noted when using the SQLAlchemy data layer) by controlling a custom element’s 'url' field to force outbound GET requests and store responses, enabling access to internal REST services and internal network probing; can be chained with CVE-2026-22218 for broader compromise.
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.