← Back
CVE-2026-45019
high
CVSS 7.2
SSRF (Server-Side Request Forgery) in chainlit (CVE-2026-45019)
Summary
SSRF in chainlit (CVE-2026-45019). Risk of unauthorized operations or information disclosure. Exploitable via `POST /mcp`. Mitigation: upgrade to `2.12.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-45019** has been found in chainlit.
Attackers can target a specific entry point like `POST /mcp` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.2/10.
What to do: upgrade chainlit to **2.12.0** or later.
If unsure, ask your IT team or search "chainlit CVE-2026-45019" on the vendor's site.
CVE-2026-45019 (chainlit) — CWE-918 / CVSS v3 7.2
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /mcp / POST /internal-admin / GET /project/settings / `sse`
Patched: `2.12.0` — apply immediately
Workaround: set features.mcp.: enabled
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.
❓ What is the problem
**SSRF** (CWE-918) exists in chainlit. Attackers reach the vulnerable code path via `POST /mcp` without authentication.
📍 Affected scope
chainlit — . Attack surface: POST /mcp / POST /internal-admin / GET /project/settings / `sse`.
🔥 Severity
Severity: High (CVSS 7.2/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.12.0**.
🛡️ Workaround
Workaround: set features.mcp.: enabled
🔍 Detection
Search webserver/proxy logs for unusual `POST /mcp` requests with malformed payloads or SQL meta-characters. Run `grep -r 'chainlit' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'POST /mcp' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `POST /mcp` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
5Apply temporary workaround mitigate
set features.mcp.: enabledパッチが適用されるまでの応急処置として、set features.mcp.: enabled を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade chainlit to 2.12.0ステージング環境で 2.12.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against POST /mcp on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
chainlit
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.12.0"}]}]