CVE-2026-61595

The multi-tenancy module (djust.tenants) in djust enforced tenant isolation only on the HTTP request path: the current tenant was stored in threading.local() and set exclusively by the HTTP-only TenantMiddleware, so on live WebSocket/SSE connections get_current_tenant() returned None during mount and in every event handler. Because the tenant-aware QuerySet manager failed OPEN in that situation — returning the unfiltered queryset even when STRICT_MODE was enabled — any query issued over the live path returned rows from every tenant. An attacker with a low-privilege account in one tenant who holds a WebSocket/SSE connection can therefore read other tenants' data (high confidentiality impact, no integrity or availability impact; CVSS 3.1 score 7.7 with scope change). All deployments running djust versions before 1.0.7 that use the djust.tenants feature together with WebSocket/SSE live connections are affected; plain HTTP-only usage is not impacted. No public proof-of-concept, KEV listing, or in-the-wild exploitation is known, and fixed version 1.0.7 is available.

What to do: Upgrade to djust 1.0.7 immediately, as there is no workaround for the live WebSocket/SSE path. Keep STRICT_MODE enabled (the default) and resolve any system check S006 warnings if STRICT_MODE was disabled; after patching, review access logs for suspicious cross-tenant reads performed over WebSocket/SSE connections.