CVE-2026-61588
- Source
- https://cve.org/CVERecord?id=CVE-2026-61588
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-61588.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-61588
- Aliases
- Published
- 2026-09-16T22:04:03Z
- Modified
- 2026-09-18T03:48:29Z
- Severity
-
- 6.5 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N CVSS Calculator
- Summary
- djust's Django model serialization has no sensitive-field denylist: password hashes, privilege flags, and PII on a public view attribute are sent to the client
- Details
-
djust provides Phoenix LiveView-style reactive server-side rendering for Django with Rust-powered performance. Prior to version 1.0.7, when a Django
Modelinstance is assigned to a public view attribute, djust serialized it to the client with no sensitive-field denylist — sending fields such aspassword(the hash), privilege flags (e.g.is_staff/is_superuser), tokens, and other PII to the browser. Because exposing model objects to templates is a normal djust pattern, this could leak credentials/PII without the developer realizing the full object crossed the wire. This is fixed in djust 1.0.7. Model serialization applies a secure-by-default sensitive-field denylist (password/hash/token/secret-style fields and known privilege flags are withheld) with an identity-subset fallback. As a workaround, keepModelinstances on_privateattributes and expose only the specific fields needed, until patched. - Database specific
{ "cna_assigner": "GitHub_M", "cwe_ids": [ "CWE-200", "CWE-359" ], "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/61xxx/CVE-2026-61588.json" }- References