Information Disclosure in djust (CVE-2026-61588)
Summary
Vulnerability in djust (CVE-2026-61588). Confidential information can be exposed externally. Exploitable via Model. Mitigation: upgrade to 1.0.7 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-61588 has been found in djust.
Attackers can target a specific entry point like Model over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade djust to 1.0.7 or later.
If unsure, ask your IT team or search "djust CVE-2026-61588" on the vendor's site.
CVE-2026-61588 (djust) — CWE-200 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: Model / password / is_staff / is_superuser
Patched: 1.0.7 — apply immediately
Workaround: Keep Model instances on _private attributes and expose only the specific fields needed, until patched.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Information disclosure (CWE-200) exists in djust. Attackers reach the vulnerable code path via Model.
Check the vendor advisory for the affected versions of djust. Attack surface: Model / password / is_staff / is_superuser.
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.
Update to 1.0.7.
Workaround: Keep Model instances on _private attributes and expose only the specific fields needed, until patched.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'djust' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'djust' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
djustを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Keep `Model` instances on `_private` attributes and expose only the specific fields needed, until patched.パッチが適用されるまでの応急処置として、Keep
Modelinstances on_privateattributes and expose only the specific fields needed, until patched. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade djust to 1.0.7ステージング環境で 1.0.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com