Vulnerability in djust (CVE-2026-61589)
Summary
Vulnerability in djust (CVE-2026-61589). Confidential information can be exposed externally. Exploitable via handle_mount. Mitigation: upgrade to 1.0.7 or later.
Original description
The description as published by the source.
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).
Patches
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.
Workarounds
No workaround on the live path short of upgrading. Most exposed when combined with STRICT_MODE=False.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-61589 has been found in djust.
Attackers can target a specific entry point like handle_mount over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.3/10.
What to do: upgrade djust to 1.0.7 or later.
If unsure, ask your IT team or search "djust CVE-2026-61589" on the vendor's site.
CVE-2026-61589 (djust) — CWE-348 / CVSS v3 6.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: handle_mount / ViewRuntime._build_request / HttpRequest / HTTP_HOST
Patched: 1.0.7 — apply immediately
Workaround: No workaround on the live path short of upgrading.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-348) exists in djust. Attackers reach the vulnerable code path via handle_mount.
Check the vendor advisory for the affected versions of djust. Attack surface: handle_mount / ViewRuntime._build_request / HttpRequest / HTTP_HOST.
Severity: Medium (CVSS 6.3/10). Confidential information can be exposed externally.
Update to 1.0.7.
Workaround: No workaround on the live path short of upgrading.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'djust' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'djust' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
djustを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
No workaround on the live path short of upgrading.パッチが適用されるまでの応急処置として、No workaround on the live path short of upgrading. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade djust to 1.0.7ステージング環境で 1.0.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com