djust is a framework providing reactive server-side rendering for Django with Rust-powered performance. Prior to version 1.0.7, it serialized Django Model instances assigned to public view attributes directly to the client without excluding sensitive fields. This resulted in exposure of sensitive data such as password hashes, privilege flags (e.g., is_staff, is_superuser), tokens, and other PII to the browser. The vulnerability arises because exposing model objects to templates is a common pattern in djust, and developers might not realize the full object is sent to the client. The vulnerability is addressed in djust 1.0.7 by applying a sensitive-field denylist that withholds password, hash, token, secret-style fields, and known privilege flags, with an identity-subset fallback. A temporary mitigation is to keep Model instances on private attributes and expose only specific fields until the patch is applied.

Exposure of sensitive information such as password hashes, privilege flags, tokens, and other personally identifiable information to unauthorized clients. This can lead to credential leakage and unauthorized access risks. The CVSS 3.1 base score is 6.5 (medium severity), reflecting network attack vector with low complexity and no user interaction required, but requiring low privileges. The impact is confidentiality loss only, with no integrity or availability impact reported.

A fix is available in djust version 1.0.7 that implements a secure-by-default sensitive-field denylist during model serialization. Users should upgrade to version 1.0.7 or later to remediate this vulnerability. Until the patch is applied, a recommended workaround is to keep Django Model instances on private attributes (e.g., _private) and expose only the specific fields needed in public view attributes to avoid leaking sensitive data.