CVE-2026-61595
HIGHDescription
djust provides Phoenix LiveView-style reactive server-side rendering for Django with Rust-powered performance. Prior to version 1.0.7, `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. This issue is 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`. No known workarounds are available on the live path.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 31% of all known CVEs.
References
Related Vulnerabilities
Other CWE-636 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2024-43532 | High | 8.8 | 12% | - | Fix |
| CVE-2023-28840 | High | 7.5 | 2.6% | - | Fix |
| CVE-2021-1578 | High | 8.8 | 2.0% | - | - |
| CVE-2023-28842 | Medium | 6.8 | 1.4% | - | Fix |
| CVE-2025-21210 | Medium | 4.2 | 1.1% | - | Fix |
| CVE-2026-53913 | Critical | 9.8 | 1.1% | - | Fix |
Common questions
How do I fix CVE-2026-61595?
No published fix for CVE-2026-61595 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-61595 being actively exploited?
Not that we know of. CVE-2026-61595 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.38% is the estimated probability that it will be exploited in the next 30 days. That is higher than 31% of all scored CVEs.
How severe is CVE-2026-61595?
CVE-2026-61595 has a CVSS v3 base score of 7.7, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-61595
Markdown
[](https://tridentstack.com/cve/CVE-2026-61595)HTML
<a href="https://tridentstack.com/cve/CVE-2026-61595"><img src="https://tridentstack.com/cve/badge/CVE-2026-61595.svg" alt="CVE-2026-61595"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-16.