# CVE-2026-61594: djust has an authorization bypass on the WebSocket/SSE mount path

> Attackers can bypass Django authorization checks on WebSocket connections to access protected views and admin functions in djust applications.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** Yes
- **Published:** 16 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-xhhm-f6hp-2qwj, PYSEC-2026-4047

## What is CVE-2026-61594?

CVE-2026-61594 is a critical authentication bypass vulnerability in djust-org djust, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

djust provides Phoenix LiveView-style reactive server-side rendering for Django with Rust-powered performance. Prior to version 1.0.7, the live (WebSocket) transport authorizes a mount via `check_view_auth`, not Django's `View.dispatch()` chain. As a result, standard Django authorization — `LoginRequiredMixin`, `PermissionRequiredMixin`, `UserPassesTestMixin`, `@method_decorator(login_required, name="dispatch")`, and custom `dispatch()` guards — and the djust admin extension's staff gate (applied only in the HTTP `as_view` wrapper) were enforced on the initial HTTP GET but silently bypassed over WebSocket, where all events and state flow. An anonymous or under-privileged client could open a WebSocket and mount such a view — including admin list/create/change/delete — and dispatch its handlers. This is fixed in djust 1.0.7. `check_view_auth` now honors the Django `AccessMixin` family on every transport; a new system check S004 fails loud at startup on auth patterns the runtime cannot safely replay (decorator/overridden-`dispatch` forms); and the admin base mixin declares `login_required = True` + an active-staff `check_permissions` gate. As a workaround, gate views using djust's `login_required` / `permission_required` / `check_permissions` attributes (honored on all transports) rather than HTTP-only mixins/decorators.

Weakness: CWE-862 (Missing Authorization), CWE-306 (Missing Authentication for Critical Functionality)

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

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-61594?

Upgrade djust to 1.0.7 or later.

## Is CVE-2026-61594 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-61594 is a critical authentication bypass vulnerability in djust-org djust, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-61594 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-61594/ (Markdown: https://insights.sbomify.com/CVE-2026-61594/index.md)
```

## Sources

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

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