https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-02T20:52:08.996191+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-372434 EUVD-2026-372434 2026-10-02T20:52:08.998614+00:00 EUVD-2026-372434 https://cve.radiocsirt.org/vuln/fkie_cve-2026-61588 fkie_cve-2026-61588 2026-10-02T20:52:08.998645+00:00

djust provides Phoenix LiveView-style reactive server-side rendering for Django with Rust-powered performance. Prior to version 1.0.7, when a Django `Model` instance is assigned to a public view attribute, djust serialized it to the client with no sensitive-field denylist — sending fields such as `password` (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, keep `Model` instances on `_private` attributes and expose only the specific fields needed, until patched.

 https://cve.radiocsirt.org/vuln/ghsa-pvg3-6q9j-mj3x GHSA-pvg3-6q9j-mj3x — djust's Django model serialization has no sensitive-field denylist: password hashes, privilege flags, and PII on a publ… 2026-10-02T20:52:08.998682+00:00

Affected: PyPI: djust

### Impact When a Django `Model` instance is assigned to a **public** view attribute, djust serialized it to the client with **no sensitive-field denylist** — sending fields such as `password` (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.

### Patches 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.

### Workarounds Keep `Model` instances on `_private` attributes and expose only the specific fields needed, until patched.

 https://cve.radiocsirt.org/vuln/pysec-2026-4045 PYSEC-2026-4045 — djust's Django model serialization has no sensitive-field denylist: password hashes, privilege flags, and PII on a publ… 2026-10-02T20:52:08.998716+00:00

Affected: PyPI: djust

### Impact When a Django `Model` instance is assigned to a **public** view attribute, djust serialized it to the client with **no sensitive-field denylist** — sending fields such as `password` (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.

### Patches 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.

### Workarounds Keep `Model` instances on `_private` attributes and expose only the specific fields needed, until patched.