Vulnerability in djust (CVE-2026-61590)
Summary
Vulnerability in djust (CVE-2026-61590). Confidential information can be exposed externally. Exploitable via eval_handler. Mitigation: upgrade to 1.0.7 or later.
Original description
The description as published by the source.
Impact
djust's observability endpoints expose live view/session state and a remote method-invocation surface (eval_handler). The localhost restriction was an opt-in middleware that the documented setup omits; the views themselves enforced only DEBUG. In the misconfigured-but-documented scenario (DEBUG on, middleware not installed) a non-localhost client could read live application state and invoke handlers remotely.
Patches
Fixed in djust 1.0.7. The localhost restriction is enforced in-view on every observability endpoint (no longer dependent on a separately-installed middleware), and eval_handler is restricted; gated requests receive a non-disclosing response.
Workarounds
Ensure DEBUG=False in production, and do not expose the observability endpoints to untrusted networks.
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-61590 has been found in djust.
Attackers can target a specific entry point like eval_handler over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.4/10.
What to do: upgrade djust to 1.0.7 or later.
If unsure, ask your IT team or search "djust CVE-2026-61590" on the vendor's site.
CVE-2026-61590 (djust) — CWE-306 / CVSS v3 7.4
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: eval_handler / DEBUG
Patched: 1.0.7 — apply immediately
Workaround: Ensure DEBUG=False in production, and do not expose the observability endpoints to untrusted networks.
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-306) exists in djust. Attackers reach the vulnerable code path via eval_handler without authentication.
Check the vendor advisory for the affected versions of djust. Attack surface: eval_handler / DEBUG.
Severity: High (CVSS 7.4/10). Confidential information can be exposed externally.
Update to 1.0.7.
Workaround: Ensure DEBUG=False in production, and do not expose the observability endpoints to untrusted networks.
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
Ensure `DEBUG=False` in production, and do not expose the observability endpoints to untrusted networks.パッチが適用されるまでの応急処置として、Ensure
DEBUG=Falsein production, and do not expose the observability endpoints to untrusted networks. を実施。回避策の副作用 (機能低下) を確認した上で。 -
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
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- package pypi.org
- web github.com
- web github.com