CVE-2026-61589

What it is

djust provides Phoenix LiveView-style reactive server-side rendering for Django with Rust-powered performance. Prior to version 1.0.7, 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). This is 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. There is no known workaround on the live path short of upgrading. Users are most exposed when combined with `STRICT_MODE=False`.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account. High risk of data exposure.

Exploit odds

0.2% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-09-16 23:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-09-30 17:51 UTC Last updatedMost recent change to the record

Details

Published

2026-09-16 23:16 UTC

Last modified

2026-09-30 17:51 UTC

Exploit probability

0.2% · EPSS, next 30 days

Weakness

CWE-348

Record status

Deferred

Attack profile CVSS 3.1 · 6.3

Attack vector

Network

Complexity

High

Privileges needed

Low

User interaction

None

Scope

Changed

Confidentiality

High

Integrity

None

Availability

None