Vulnerability in djust (CVE-2026-61599)
Summary
Vulnerability in djust (CVE-2026-61599). Risk of unauthorized operations or information disclosure. Exploitable via LiveView. Mitigation: upgrade to 1.0.7 or later.
Original description
The description as published by the source.
Impact
The djust live transport resolves the LiveView to mount from a client-supplied dotted path by calling __import__(module_path, ...). The module is imported — running its top-level code (import side effects) — before the framework checks that the resolved object is a LiveView subclass and before any per-view authentication. The LIVEVIEW_ALLOWED_MODULES allowlist that should contain this is fail-open (if allowed_modules: — skipped when the setting is unset, the framework default) and uses loose startswith matching.
An unauthenticated WebSocket client (the WS handshake does not require auth; per-view auth runs only after import + instantiate) can therefore send a mount / live_redirect_mount / url_change frame (or an SSE mount) with view = ".AnyName" and cause the server to import — and execute the top-level code of — any importable Python module by name.
Consequences: server-side execution of arbitrary importable modules' import-time side effects by an unauthenticated client (effectively RCE-by-proxy on any host that has a side-effectful importable module), denial of service (import bombs / expensive dependency trees), and a module/class enumeration oracle via distinct error strings.
Reproduced end-to-end: an unauthenticated WebsocketCommunicator mount frame with the allowlist unset imported and executed a sentinel non-LiveView module before the "not a LiveView subclass" rejection.
Affected code
- `python/dj…
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-61599 has been found in djust.
Attackers can target a specific entry point like LiveView over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade djust to 1.0.7 or later.
If unsure, ask your IT team or search "djust CVE-2026-61599" on the vendor's site.
CVE-2026-61599 (djust) — CWE-470
Attack surface: LiveView / LIVEVIEW_ALLOWED_MODULES / startswith / mount
Patched: 1.0.7 — apply immediately
Workaround: Set LIVEVIEW_ALLOWED_MODULES to the narrow list of modules that contain your mountable LiveView classes.
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-470) exists in djust. Attackers reach the vulnerable code path via LiveView.
Check the vendor advisory for the affected versions of djust. Attack surface: LiveView / LIVEVIEW_ALLOWED_MODULES / startswith / mount.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.0.7.
Workaround: Set LIVEVIEW_ALLOWED_MODULES to the narrow list of modules that contain your mountable LiveView classes.
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
Set `LIVEVIEW_ALLOWED_MODULES` to the narrow list of modules that contain your mountable LiveView classes.パッチが適用されるまでの応急処置として、Set
LIVEVIEW_ALLOWED_MODULESto the narrow list of modules that contain your mountable LiveView classes. を実施。回避策の副作用 (機能低下) を確認した上で。 -
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