# CVE-2026-61593: djust has Cross-Site Request Forgery on the Server-Sent-Events transport: a cross-origin page can drive a victim-authenticated SSE session

> Attackers can force victim-authenticated SSE sessions to execute state-changing actions via cross-origin requests due to missing CSRF protections.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 16 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-pg97-jvmf-qfvc, PYSEC-2026-4044

## What is CVE-2026-61593?

CVE-2026-61593 is a high-severity vulnerability in djust-org djust, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2026-61593?

3 open source packages ship an affected version, including djust.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `djust` | PyPI | All versions | 1.0.7 |
| `djust` | PyPI | All versions | 1.0.7 |
| `djust` | PyPI | All versions | 1.0.7 |

## How do I fix CVE-2026-61593?

Upgrade djust to 1.0.7 or later.

## Is CVE-2026-61593 being exploited?

There is no known exploitation of CVE-2026-61593 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-61593 and fix it if it is affected.

What it is: CVE-2026-61593 is a high-severity vulnerability in djust-org djust, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-61593 in the wild and no public exploit code.

Affected packages and fixed versions:
- djust (PyPI): affected all versions; fixed in 1.0.7
- djust (PyPI): affected all versions; fixed in 1.0.7
- djust (PyPI): affected all versions; fixed in 1.0.7

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-61593/ (Markdown: https://insights.sbomify.com/CVE-2026-61593/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-61593
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-61593
- OSV: https://osv.dev/vulnerability/CVE-2026-61593

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-61593/
Summaries are generated and may contain mistakes; the official description above is the record.