# CVE-2026-61588: 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

> djust library leaks sensitive model fields like password hashes and PII to clients when models are assigned to public view attributes.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Sep 2026
- **Updated:** 19 Sep 2026
- **Also known as:** GHSA-pvg3-6q9j-mj3x, PYSEC-2026-4045

## What is CVE-2026-61588?

CVE-2026-61588 is a medium-severity vulnerability in djust-org djust, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-359 (Exposure of Private Personal Information to an Unauthorized Actor), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-61588?

3 open source packages ship an affected version, including djust.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `djust` | PyPI | All versions | 1.0.7 |
| `djust` | PyPI | All versions | 1.0.7 |
| `djust` | PyPI | All versions | 1.0.7 |

## How do I fix CVE-2026-61588?

Upgrade djust to 1.0.7 or later.

## Is CVE-2026-61588 being exploited?

There is no known exploitation of CVE-2026-61588 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-61588 and fix it if it is affected.

What it is: CVE-2026-61588 is a medium-severity vulnerability in djust-org djust, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-61588 in the wild and no public exploit code.

Affected packages and fixed versions:
- djust (PyPI): affected all versions; fixed in 1.0.7
- djust (PyPI): affected all versions; fixed in 1.0.7
- djust (PyPI): affected all versions; fixed in 1.0.7

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-61588/ (Markdown: https://insights.sbomify.com/CVE-2026-61588/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-61588
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-61588
- OSV: https://osv.dev/vulnerability/CVE-2026-61588

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-61588/
Summaries are generated and may contain mistakes; the official description above is the record.