Is djust affected by CVE-2026-61589?

PyPI djust is affected in < 1.0.7.

Is CVE-2026-61589 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.2%.

← All vulnerabilities

MEDIUMSupply chain

CVE-2026-61589

Q: Is CVE-2026-61589 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.2%.

PyPI · djust

Summary

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

Advisory details

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 TenantResolvers 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

Related vulnerabilities

All Supply chain →