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
Impact djust's LiveViewConsumer mounts a LiveView over a WebSocket. When a view is gated (loginrequired / permissionrequired, or an onmount hook that returns a redirect) and the connecting user is not authorized, the consumer sent the client a {"type":"navigate","to":...} redirect frame and then returned — without closing the socket and without clearing self.viewinstance.
Published Aug 25, 2026
Affected packages
djust
- Ecosystem
- PyPI
- Affected
- < 1.0.4
- Fixed in
- 1.0.4
- Check
pip show djust
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
djust's LiveViewConsumer mounts a LiveView over a WebSocket. When a view is gated (login_required / permission_required, or an on_mount hook that returns a redirect) and the connecting user is not authorized, the consumer sent the client a {"type":"navigate","to":...} redirect frame and then returned — without closing the socket and without clearing `self.view_instance`. Only the PermissionDenied branch closed the connection (close(4403)).
A real browser obeys the navigate frame and leaves, hiding the problem. A raw WebSocket client that ignores the redirect keeps an open, mounted socket. Because handle_event did not re-check authentication/authorization after mount, that client could then send {"type":"event", ...} frames and invoke any @event_handler method on the gated view with no authenticated session — an authentication bypass on the live mutation path.
Who is affected: apps that expose LiveViews gated by login_required / permission_required / a redirecting on_mount hook, where the gated view's event handlers perform sensitive reads or mutations and do not independently re-verify the user. Exploitation requires a non-browser WebSocket client and knowledge (or enumeration) of the view path and event names.
Patches
Fixed in djust 1.0.4 (commit 1ae8aa9, PR #1780). Both the auth-redirect and on_mount-hook-redirect branches of handle_mount now send the navigate frame and then `close(code=4403)` and clear `self.view_instance`, mirroring the existing PermissionDenied branch. Public / authorized mounts are unchanged. The same path is reachable via handle_live_redirect_mount (which delegates to handle_mount) and is covered by the same fix.
1.0.4 also adds an opt-in defense-in-depth control, LIVEVIEW_CONFIG['reauth_on_event'] = True (default OFF), which re-resolves the user from the session and re-runs the view's auth check on every event for gated views.
Workarounds
Upgrade to 1.0.4. If you cannot upgrade immediately, on affected versions ensure that every `@event_handler` on a gated `LiveView` independently verifies the request user is authenticated and authorized (e.g. check request.user.is_authenticated / permissions at the top of each handler), since the framework does not re-check after mount on < 1.0.4. Alternatively, override the consumer's handle_mount to await self.close(code=4403) after emitting an auth redirect.
Proof of concept
Using Channels' WebsocketCommunicator against LiveViewConsumer.as_asgi() with an anonymous scope, mount a login_required view: the server emits a navigate frame but the socket stays open. Sending a subsequent {"type":"event", "handler":"<mutating_handler>", ...} frame reaches the handler and executes it without an authenticated session. On 1.0.4 the socket is closed with code 4403 immediately after the redirect and the event frame is rejected. (Regression test: tests/test_ws_auth_close_socket.py.)
Credits
Discovered internally during the djust v1.1.0 WebSocket-auth security review.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-113731
djust: Arbitrary absolute-path file read in the find_handlers_for_template MCP tool
low3.3Oct 21, 2026GHSA-9395-2g46-rj3f
djust: Six template-layer defects emit attacker-controlled markup unescaped (XSS)
highSep 17, 2026CVE-2026-125112
djust: A template binding inherits a context safety grant it never earned (XSS)
high8.7Sep 17, 2026CVE-2026-61588
djust's Django model serialization has no sensitive-field denylist: password hashes, privilege flags, and PII on a public view attribute are sent to the client
medium6.5Sep 16, 2026CVE-2026-61589
djust: WebSocket/runtime reconstructed request omits the client Host, causing host/subdomain TenantResolvers to misresolve the tenant on the live path
medium6.3Sep 16, 2026CVE-2026-61590
djust's observability endpoints are network-exposed: the localhost gate is an opt-in middleware the docs omit, and the views enforce only DEBUG
high7.4Sep 16, 2026
