← Back
CVE-2025-59152
Vulnerability in litestar (CVE-2025-59152)
Summary
vulnerability in litestar (CVE-2025-59152). Risk of unauthorized operations or information disclosure. Exploitable via ``SECURE_PROXY_SSL_HEADER``. Mitigation: upgrade to `2.18.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-59152** has been found in litestar.
Attackers can target a specific entry point like ``SECURE_PROXY_SSL_HEADER`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade litestar to **2.18.0** or later.
If unsure, ask your IT team or search "litestar CVE-2025-59152" on the vendor's site.
CVE-2025-59152 (litestar) — CWE-807 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `SECURE_PROXY_SSL_HEADER`
Patched: `2.18.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.
❓ What is the problem
**A vulnerability** (CWE-807) exists in litestar. Attackers reach the vulnerable code path via ``SECURE_PROXY_SSL_HEADER`` without authentication.
📍 Affected scope
litestar — . Attack surface: `SECURE_PROXY_SSL_HEADER`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.18.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'litestar' .` 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 'litestar' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `litestar` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade litestar to 2.18.0ステージング環境で 2.18.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
litestar
[{"type":"ECOSYSTEM","events":[{"introduced":"2.17.0"},{"fixed":"2.18.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-59152
- advisory https://github.com/advisories/GHSA-hm36-ffrh-c77c
- package https://github.com/litestar-org/litestar
- package https://pypi.org/project/litestar
- web https://github.com/litestar-org/litestar/security/advisories/GHSA-hm36-ffrh-c77c
- web https://github.com/litestar-org/litestar/commit/42a89e043e50b515f8548a93954fe143f63cf9fb
- web https://github.com/litestar-org/litestar/blob/26f20ac6c52de2b4bf81161f7560c8bb4af6f382/litestar/middleware/rate_limit.py#L127