Vulnerability in djust (CVE-2026-61591)
Summary
Vulnerability in djust (CVE-2026-61591). Confidential information can be exposed externally. Exploitable via state_json. Mitigation: upgrade to 1.0.7 or later.
Original description
The description as published by the source.
Impact
For views that opt into state snapshots, the snapshot state_json embedded in the client page was restored on reconnect as trusted view state with no integrity check. A client could edit the unsigned state_json in their page and return it in the reconnect mount frame to inject arbitrary view attributes — e.g. flip is_admin to True, or change account_id / balance — escalating privilege or tampering with business state held in public view attributes (the normal djust pattern).
Patches
Fixed in djust 1.0.7. State snapshots are signed; unsigned or forged snapshots are rejected on the back-navigation restore path.
Workarounds
Do not enable state snapshots; do not hold authorization/ownership state in public view attributes.
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-61591 has been found in djust.
Attackers can target a specific entry point like state_json over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: upgrade djust to 1.0.7 or later.
If unsure, ask your IT team or search "djust CVE-2026-61591" on the vendor's site.
CVE-2026-61591 (djust) — CWE-345 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: state_json / is_admin / True / account_id
Patched: 1.0.7 — apply immediately
Workaround: Do not enable state snapshots; do not hold authorization/ownership state in public view attributes.
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-345) exists in djust. Attackers reach the vulnerable code path via state_json.
Check the vendor advisory for the affected versions of djust. Attack surface: state_json / is_admin / True / account_id.
Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.
Update to 1.0.7.
Workaround: Do not enable state snapshots; do not hold authorization/ownership state in public view attributes.
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
Do not enable state snapshots; do not hold authorization/ownership state in public view attributes.パッチが適用されるまでの応急処置として、Do not enable state snapshots; do not hold authorization/ownership state in public view attributes. を実施。回避策の副作用 (機能低下) を確認した上で。
-
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