Cross-Site Request Forgery (CSRF) in djust (CVE-2026-61593)
Summary
Vulnerability in djust (CVE-2026-61593). Confidential information can be exposed externally. Exploitable via session_id. Mitigation: upgrade to 1.0.7 or later.
Original description
The description as published by the source.
Impact
The SSE client→server POST endpoints are @csrf_exempt and the SSE GET stream endpoint had no Origin check, so a cross-origin page could drive a victim-cookie-authenticated SSE session: force the victim's browser to GET the stream URL (which creates and mounts a LiveView as the victim) and POST to the message endpoint with credentials: include to fire state-changing event handlers as the victim. The URL session_id is client-chosen (validated only for UUID format), so it is not a CSRF token, and a JSON body sent as text/plain is a CORS simple request with no preflight.
Patches
Fixed in djust 1.0.7. All three SSE endpoints validate the request Origin against ALLOWED_HOSTS (mirroring the WebSocket CSWSH defense) and reject cross-origin requests with 403; the POST endpoints additionally require Content-Type: application/json (415 otherwise), closing the text/plain simple-request bypass.
Workarounds
Disable the SSE transport, or front it with a proxy that enforces an Origin allowlist.
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-61593 has been found in djust.
Attackers can target a specific entry point like session_id over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: upgrade djust to 1.0.7 or later.
If unsure, ask your IT team or search "djust CVE-2026-61593" on the vendor's site.
CVE-2026-61593 (djust) — CWE-352 / CVSS v3 8.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: session_id / Origin / ALLOWED_HOSTS
Patched: 1.0.7 — apply immediately
Workaround: Disable the SSE transport, or front it with a proxy that enforces an Origin allowlist.
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.
CSRF (CWE-352) exists in djust. Attackers reach the vulnerable code path via session_id without authentication.
Check the vendor advisory for the affected versions of djust. Attack surface: session_id / Origin / ALLOWED_HOSTS.
Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.
Update to 1.0.7.
Workaround: Disable the SSE transport, or front it with a proxy that enforces an Origin allowlist.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'djust' . 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 'djust' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
djustを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Disable the SSE transport, or front it with a proxy that enforces an Origin allowlist.パッチが適用されるまでの応急処置として、Disable the SSE transport, or front it with a proxy that enforces an Origin allowlist. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade djust to 1.0.7ステージング環境で 1.0.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- package pypi.org
- web github.com
- web github.com