What is CVE-2026-61595?

CVE-2026-61595 is a high-severity missing authorization vulnerability in djust (pip), affecting versions < 1.0.7. It is fixed in 1.0.7. The application does not perform an authorization check before performing a sensitive operation.

How severe is CVE-2026-61595?

CVE-2026-61595 has a CVSS score of 7.7 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of djust are affected by CVE-2026-61595?

djust (pip) versions < 1.0.7 is affected.

Is there a fix for CVE-2026-61595?

Yes. CVE-2026-61595 is fixed in 1.0.7. Upgrade to this version or later.

Is CVE-2026-61595 exploitable, and should I be worried?

Whether CVE-2026-61595 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-61595 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-61595?

Upgrade djust to 1.0.7 or later.

CVE-2026-61595 in djust

Q: How severe is CVE-2026-61595?

CVE-2026-61595 has a CVSS score of 7.7 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of djust are affected by CVE-2026-61595?

djust (pip) versions < 1.0.7 is affected.

Q: Is there a fix for CVE-2026-61595?

Yes. CVE-2026-61595 is fixed in 1.0.7. Upgrade to this version or later.

Q: Is CVE-2026-61595 exploitable, and should I be worried?

Whether CVE-2026-61595 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-61595 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-61595?

Upgrade djust to 1.0.7 or later.

Summary

djust: Multi-tenant isolation fails open on the WebSocket/SSE path, disclosing other tenants' data

Workarounds

No workaround on the live path short of upgrading.

Impact

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.

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

CVE-2026-61595 has a CVSS score of 7.7 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.0.7); upgrading removes the vulnerable code path.

Affected versions

djust (< 1.0.7)

Security releases

djust → 1.0.7 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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.

Frequently Asked Questions

What is CVE-2026-61595? CVE-2026-61595 is a high-severity missing authorization vulnerability in djust (pip), affecting versions < 1.0.7. It is fixed in 1.0.7. The application does not perform an authorization check before performing a sensitive operation.
How severe is CVE-2026-61595? CVE-2026-61595 has a CVSS score of 7.7 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of djust are affected by CVE-2026-61595? djust (pip) versions < 1.0.7 is affected.
Is there a fix for CVE-2026-61595? Yes. CVE-2026-61595 is fixed in 1.0.7. Upgrade to this version or later.
Is CVE-2026-61595 exploitable, and should I be worried? Whether CVE-2026-61595 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-61595 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-61595? Upgrade djust to 1.0.7 or later.