Advisory

GHSA-3492-cvg7-9mr2

Also known as: CVE-2026-61595, PYSEC-2026-4036

Summary

djust: Multi-tenant isolation fails open on the WebSocket/SSE path, disclosing other tenants' data

Details

Impact
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.

Patches
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.

Workarounds
No workaround on the live path short of upgrading.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-09-16 15:32 UTC
Modified
2026-10-01 17:56 UTC

Affected packages and fixes

djust

PyPI · All systems

Affected

  • introduced 0, fixed 1.0.7 (ecosystem)

Fixed versions

1.0.7

Fix

  • Fixed version 1.0.7
    pip install --upgrade djust==1.0.7

Fix 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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences