CVE-2026-61591

published 16 Sep 2026 · updated 17 Sep 2026

djust: Unsigned client state snapshot is restored as trusted view state (privilege escalation / state injection)

8.1HighCVSS 8.1EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

djust provides Phoenix LiveView-style reactive server-side rendering for Django with Rust-powered performance. Prior to version 1.0.7, 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). This issue is fixed in djust 1.0.7. State snapshots are signed; unsigned or forged snapshots are rejected on the back-navigation restore path. As a workaround, do not enable state snapshots; do not hold authorization/ownership state in public view attributes.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
djust-org<1.0.7

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-61591 severity on Zeptric[![CVE-2026-61591](https://zeptric.io/badge/cve/CVE-2026-61591.svg)](https://zeptric.io/cve/CVE-2026-61591)