Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-c67v-vqrp-m5wj

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

CVSS 8.1 HighEPSS 0.0022 · 13th percentile

Published by the GitHub Advisory Database at 16 Sept 2026, 21:56 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
djustPyPI<1.0.71.0.7
Identifiers
GHSA-c67v-vqrp-m5wj · CVE-2026-61591 · PYSEC-2026-4040
Weakness (CWE)
CWE-345 · CWE-915
Tags
Published
16 Sept 2026
Updated
1 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The djust package, versions before 1.0.7, restores client-side state snapshots on reconnect as trusted view state without an integrity check. An attacker who can use a client session for a view that opts into state snapshots can edit the unsigned state in the page and inject arbitrary view attributes, such as changing an admin flag or account and balance values. Upgrade to djust 1.0.7, which signs state snapshots and rejects unsigned or forged ones. Until then, avoid enabling state snapshots and do not keep authorization or ownership data in public view attributes.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.1 High 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0022, the 13th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:09 UTC First seen by agentprime
  2. 31 Oct 2026, 14:09 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.