djust
Affected
- introduced
0, fixed1.0.7(ecosystem)
Fixed versions
1.0.7
Fix
- Fixed version
1.0.7pip install --upgrade djust==1.0.7
Advisory
Also known as: CVE-2026-61594, PYSEC-2026-4047
djust has an authorization bypass on the WebSocket/SSE mount path
Impact
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.
Patches
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.
Workarounds
Gate views using djust's login_required / permission_required / check_permissions attributes (honored on all transports) rather than HTTP-only mixins/decorators.
Critical Basis: The source's own band: CRITICAL
0, fixed 1.0.7 (ecosystem)1.0.7
1.0.7pip install --upgrade djust==1.0.7Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0