SSRF (Server-Side Request Forgery) in chainlit (CVE-2026-22219)
Summary
SSRF in chainlit (CVE-2026-22219). Confidential information can be exposed externally. Mitigation: upgrade to 2.9.4 or later.
Original description
The description as published by the source.
Chainlit versions prior to 2.9.4 contain a server-side request forgery (SSRF) vulnerability in the /project/element update flow when configured with the SQLAlchemy data layer backend. An authenticated client can provide a user-controlled url value in an Element, which is fetched by the SQLAlchemy element creation logic using an outbound HTTP GET request. This allows an attacker to make arbitrary HTTP requests from the Chainlit server to internal network services or cloud metadata endpoints and store the retrieved responses via the configured storage provider.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-22219 has been found in chainlit.
Confidential information can be exposed externally. CVSS score: 7.7/10.
What to do: upgrade chainlit to 2.9.4 or later.
If unsure, ask your IT team or search "chainlit CVE-2026-22219" on the vendor's site.
CVE-2026-22219 (chainlit) — CWE-918 / CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
Patched: 2.9.4 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SSRF (CWE-918) exists in chainlit.
Check the vendor advisory for the affected versions of chainlit.
Severity: High (CVSS 7.7/10). Confidential information can be exposed externally.
Update to 2.9.4.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'chainlit' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'chainlit' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
chainlitを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade chainlit to 2.9.4ステージング環境で 2.9.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory disclosure@vulncheck.com
- advisory nvd.nist.gov
- advisory github.com
- exploit disclosure@vulncheck.com
- package github.com
- package pypi.org
- web disclosure@vulncheck.com
- web github.com