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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

EPSS

• CVE-2026-61591: 0.22% estimated exploitation activity in the next 30 days; percentile 13.29 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact For views that opt into state snapshots, the snapshot statejson embedded in the client page was restored on reconnect as trusted view state with no integrity check. A client could edit the unsigned statejson in their page and return it in the reconnect mount frame to inject arbitrary view attributes — e.g. flip isadmin to True, or change accountid / 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.

Published by the source

16 Sep 2026, 21:56 UTC

Last modified by the source

1 Oct 2026, 17:55 UTC

Source last checked

26 Oct 2026, 13:52 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-c67v-vqrp-m5wj

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-c67v-vqrp-m5wj

3. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-c67v-vqrp-m5wj

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-61591

Advisory: djust: Unsigned client state snapshot is restored as trusted view state (privilege escalation / state injection)
IDs: CVE-2026-61591, GHSA-c67v-vqrp-m5wj
Record: https://patchnext.com/advisories/cve-2026-61591 (revision 3, source checked 26 Oct 2026, 13:52 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: djust 1.0.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI djust: affected < 1.0.7; fixed in 1.0.7

## Suggested inspection (read-only)
- `python -m pip show djust`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on djust.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-c67v-vqrp-m5wj (GitHub-reviewed advisory GHSA-c67v-vqrp-m5wj lists affected ranges: PyPI djust >=0 <1.0.7)
- Verified: https://osv.dev/vulnerability/GHSA-c67v-vqrp-m5wj (OSV record GHSA-c67v-vqrp-m5wj lists affected ranges: PyPI djust >=0 <1.0.7 (fixed))

Commands are suggestions: review each one before running it.