What is CVE-2026-61589?

CVE-2026-61589 is a medium-severity security vulnerability in djust (pip), affecting versions < 1.0.7. It is fixed in 1.0.7.

How severe is CVE-2026-61589?

CVE-2026-61589 has a CVSS score of 6.3 (Medium). 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-61589?

djust (pip) versions < 1.0.7 is affected.

Is there a fix for CVE-2026-61589?

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

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

Whether CVE-2026-61589 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-61589 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-61589?

Upgrade djust to 1.0.7 or later.

CVE-2026-61589 in djust

Q: How severe is CVE-2026-61589?

CVE-2026-61589 has a CVSS score of 6.3 (Medium). 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-61589?

djust (pip) versions < 1.0.7 is affected.

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

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

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

Whether CVE-2026-61589 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-61589 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-61589?

Upgrade djust to 1.0.7 or later.

Summary

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

Workarounds

No workaround on the live path short of upgrading. Most exposed when combined with STRICT_MODE=False.

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

CVE-2026-61589 has a CVSS score of 6.3 (Medium). 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. 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.

Frequently Asked Questions

What is CVE-2026-61589? CVE-2026-61589 is a medium-severity security vulnerability in djust (pip), affecting versions < 1.0.7. It is fixed in 1.0.7.
How severe is CVE-2026-61589? CVE-2026-61589 has a CVSS score of 6.3 (Medium). 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-61589? djust (pip) versions < 1.0.7 is affected.
Is there a fix for CVE-2026-61589? Yes. CVE-2026-61589 is fixed in 1.0.7. Upgrade to this version or later.
Is CVE-2026-61589 exploitable, and should I be worried? Whether CVE-2026-61589 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-61589 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-61589? Upgrade djust to 1.0.7 or later.