# CVE-2026-61589 — djust-org djust

> As of 2026-09-17, CVE-2026-61589 is a MEDIUM-severity vulnerability in djust-org djust, CVSS v3.1 6.3. No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-61589 as of 2026-09-17; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-09-17

## What is CVE-2026-61589?

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

The record classifies CVE-2026-61589 under weakness classes [CWE-348](https://cwe.mitre.org/data/definitions/348.html), [CWE-639](https://intel.threadlinqs.com/cwe/CWE-639). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs low-privilege credentials, needs no user interaction, and has high impact on confidentiality. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 19 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 6.3 — MEDIUM (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 3.2/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-09-16, last modified 2026-09-17

## Is CVE-2026-61589 being exploited?

It currently carries a trending score of 30 in the Threadlinqs vulnerability feed.

## Affected products and versions

- **djust-org**: djust

## How to fix CVE-2026-61589

No vendor patch reference has been recorded for CVE-2026-61589 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-61589

No threat campaign in the Threadlinqs corpus currently references CVE-2026-61589, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD. Last verified by Threadlinqs on 2026-09-17. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [github.com](https://github.com/djust-org/djust/security/advisories/GHSA-v9rj-xjfv-xj9r)

**Other references**

- [github.com](https://github.com/djust-org/djust/releases/tag/v1.0.7)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-61589
Full detection coverage and IOCs for threats exploiting CVE-2026-61589 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp