CVE-2026-61595 djust: Multi-tenant isolation fails open on the WebSocket/SSE path, disclosing other tenants' data
Attackers can access other tenants' data via WebSocket/SSE connections due to failed tenant isolation in the djust library.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-61595?
CVE-2026-61595 is a high-severity missing authorization vulnerability in djust-org djust, published on 16 Sep 2026. Any signed-in user can exploit it over the network, 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, `djust.tenants` isolation was enforced only on the HTTP path. The current tenant was stored in `threading.local()` and set exclusively by the HTTP-only `TenantMiddleware`, so on the live (WebSocket/SSE) path `get_current_tenant()` was always `None` during mount and every event handler — and the tenant-aware `QuerySet` manager failed OPEN (returned the unfiltered queryset, ignoring `STRICT_MODE`), disclosing every tenant's rows to whoever held the socket. `threading.local` was additionally shared across connections on the `sync_to_async` executor thread. This issue is fixed in djust 1.0.7. Tenant storage moved to a `contextvars.ContextVar` (per async task); the resolved tenant is bound around WS/SSE mount and every dispatch; both managers scope the base queryset once and fail CLOSED (`.none()` under the default `STRICT_MODE`); and system check S006 warns when `STRICT_MODE=False`. No known workarounds are available on the live path.
Which versions are affected by CVE-2026-61595?
3 open source packages ship an affected version, including djust.
| Package | 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-61595?
Upgrade djust to 1.0.7 or later.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-61595 being exploited?
There is no known exploitation of CVE-2026-61595 in the wild and no public exploit code.
Sources
Also known as GHSA-3492-cvg7-9mr2, PYSEC-2026-4036.