CVE-2026-61593
Last modified
CVE-2026-61593 is a high-severity vulnerability rated 8.1/10 on the CVSS scale. djust provides Phoenix LiveView-style reactive server-side rendering for Django with Rust-powered performance. Prior to version 1.0.7, 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. EPSS estimates a 0.21% chance of exploitation in the next 30 days.
Description
djust provides Phoenix LiveView-style reactive server-side rendering for Django with Rust-powered performance. Prior to version 1.0.7, 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. The issue is fixed in 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. As a workaround, disable the SSE transport, or front it with a proxy that enforces an Origin allowlist.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| djust-org | djust | < 1.0.7 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-61593?
How severe is CVE-2026-61593?
How do I fix CVE-2026-61593?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-61588djust provides Phoenix LiveView-style reactive server-side r…6.5
- CVE-2026-61589djust provides Phoenix LiveView-style reactive server-side r…6.3
- CVE-2026-6159A vulnerability has been found in code-projects Simple ChatB…4.3
- CVE-2026-61590djust provides Phoenix LiveView-style reactive server-side r…7.4
- CVE-2026-61591djust provides Phoenix LiveView-style reactive server-side r…8.1
- CVE-2026-61592djust provides Phoenix LiveView-style reactive server-side r…7.4
- CVE-2026-61594djust provides Phoenix LiveView-style reactive server-side r…9.1
- CVE-2026-61595djust provides Phoenix LiveView-style reactive server-side r…7.7
- CVE-2026-61596djust provides Phoenix LiveView-style reactive server-side r…7.1
- CVE-2026-61597djust provides Phoenix LiveView-style reactive server-side r…5.1
- CVE-2026-61598djust provides Phoenix LiveView-style reactive server-side r…7.1
- CVE-2026-61599djust provides Phoenix LiveView-style reactive server-side r…8.8
Are you affected by CVE-2026-61593?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
