Cross-Site Scripting (XSS) in litestar (CVE-2026-48060)
Summary
Cross-site scripting in litestar (CVE-2026-48060). Confidential information can be exposed externally. Exploitable via GET /vulnerable. Mitigation: upgrade to 2.22.0 or later.
Original description
The description as published by the source.
Litestar is an Asynchronous Server Gateway Interface (ASGI) framework. Prior to version 2.20.0, Litestar instances which use a template engine in conjunction with CSRF protection are vulnerable to HTML Injection which can be escalated to Cross Site Scripting due to the contents of the CSRF cookie being excluded from automatic escaping by the template engine when configured inline with documentation recommendations. This issue has been patched in version 2.20.0.
Source: GitHub Security Advisories (Global) 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-48060 has been found in litestar.
Attackers can target a specific entry point like GET /vulnerable over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: upgrade litestar to 2.22.0 or later.
If unsure, ask your IT team or search "litestar CVE-2026-48060" on the vendor's site.
CVE-2026-48060 (litestar) — CWE-79 / CVSS v3 8.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: GET /vulnerable / input / csrftoken / poc2.py
Patched: 2.22.0 — 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.
Cross-site scripting (XSS) (CWE-79) exists in litestar. Attackers reach the vulnerable code path via GET /vulnerable without authentication.
Check the vendor advisory for the affected versions of litestar. Attack surface: GET /vulnerable / input / csrftoken / poc2.py.
Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.
Update to 2.22.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /vulnerable requests with malformed payloads or SQL meta-characters. Run grep -r 'litestar' . 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 'litestar' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
litestarを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /vulnerable' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /vulnerableへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade litestar to 2.22.0ステージング環境で 2.22.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /vulnerable on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web docs.litestar.dev
- web github.com
- web github.com