# CVE-2026-55571: djust authentication bypass: a login_required / on_mount LiveView mount redirect does not close the WebSocket, allowing an unauthenticated client to dispatch event-handler calls

> Unauthenticated attackers can bypass LiveView mount redirects to execute event handlers, enabling unauthorized data access or modification in djust applications.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 25 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** GHSA-xx4j-w367-7247, PYSEC-2026-3829

## What is CVE-2026-55571?

CVE-2026-55571 is a high-severity authentication bypass vulnerability in djust-org djust, published on 25 Aug 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 1.0.4, LiveViewConsumer.handle_mount sends a `{"type":"navigate","to":...}` frame when login_required, permission_required, or a redirecting on_mount hook denies a LiveView mount, but returns without closing the WebSocket or clearing self.view_instance. A browser follows the redirect, but a raw WebSocket client can ignore it and retain the mounted socket. Because LiveViewConsumer.handle_event does not recheck authentication or authorization, the client can send `{"type":"event",...}` frames that invoke @event_handler methods without an authenticated session, including through handle_live_redirect_mount, enabling unauthorized sensitive reads or mutations. This issue is fixed in version 1.0.4.

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

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

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


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

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

Upgrade djust to 1.0.4 or later.

## Is CVE-2026-55571 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55571 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-55571 is a high-severity authentication bypass vulnerability in djust-org djust, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55571 exists.

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

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-55571/ (Markdown: https://insights.sbomify.com/CVE-2026-55571/index.md)
```

## Sources

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

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