~ / search / GHSA-v9rj-xjfv-xj9r

GHSA-v9rj-xjfv-xj9r

djust: WebSocket/runtime reconstructed request omits the client Host, causing host/subdomain TenantResolvers to misresolve the tenant on the live path

Source: GitHub Advisory Database (reviewed) Moderate CVE-2026-61589

Packages

EcosystemPackageAffectedFixed in
PyPI djust < 1.0.7 1.0.7

Details

As written in the advisory (Markdown source, shown as plain text).

### Impact The WebSocket `handle_mount` and `ViewRuntime._build_request` rebuild an `HttpRequest` via `RequestFactory().get(...)` with no `HTTP_HOST`, so `request.get_host()` defaulted to `"testserver"` on the live path. Host/subdomain/domain `TenantResolver`s then misresolved the tenant — `None` on the live path while the HTTP path resolved correctly. With `STRICT_MODE=False` the tenant-scoped managers returned unscoped rows (**cross-tenant disclosure**); with the default they returned an empty queryset (broken tenancy). ### Patches Fixed in **djust 1.0.7**. The handshake Host is extracted from the ASGI scope, validated against `ALLOWED_HOSTS` (the same logic as the CSWSH Origin gate, parsed with Django's `split_domain_port` so malformed Hosts are rejected at the boundary), and propagated — with the TLS scheme — into the reconstructed request, so live-path tenant resolution matches HTTP exactly. ### Workarounds No workaround on the live path short of upgrading. Most exposed when combined with `STRICT_MODE=False`.

References

External links from the advisory. They lead to third-party sites.