---
id: CVE-2026-61598
title: >-
  djust provides Phoenix LiveView-style reactive server-side rendering for
  Django with Rust-powered performance
summary: >-
  djust provides Phoenix LiveView-style reactive server-side rendering for
  Django with Rust-powered performance. Prior to version 1.0.7,
  `djust.mixins.model_binding.ModelBindingMixin` provides a default
  `update_model` event handler and is …
severity: high
cvss: 7.1
cvssVector: 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N'
cwe:
  - CWE-915
vendor: djust
product: djust
affected:
  - djust < 1.0.7
patched:
  - djust 1.0.7
published: '2026-09-16'
updated: '2026-09-16'
sourceUpdated: '2026-09-16T16:17:14.220'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-61598'
references:
  - url: 'https://github.com/djust-org/djust/releases/tag/v1.0.7'
    label: security-advisories@github.com
  - url: 'https://github.com/djust-org/djust/security/advisories/GHSA-cc7c-9jff-58wj'
    label: security-advisories@github.com
  - url: 'https://github.com/advisories/GHSA-cc7c-9jff-58wj'
  - url: 'https://github.com/djust-org/djust'
tags:
  - nvd
  - ghsa
  - pip
  - cve.org
  - osv
aliases:
  - GHSA-cc7c-9jff-58wj
ecosystem: pip
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2026-09-16T15:27:26.525288Z'
cvssSource: cna
ingestedAt: '2026-09-16T13:56:12.613Z'
epss: 0.00411
epssPercentile: 0.35056
---

## Overview

djust provides Phoenix LiveView-style reactive server-side rendering for Django with Rust-powered performance. Prior to version 1.0.7, `djust.mixins.model_binding.ModelBindingMixin` provides a default `update_model` event handler and is part of the LiveView base MRO, so every LiveView exposes it. It `setattr`s a view attribute whose name is client-supplied (`field`), gated only by: reject `_`-prefixed names; reject a 14-entry denylist of framework internals (`FORBIDDEN_MODEL_FIELDS`); optional `allowed_model_fields` which defaults to None = allow all; and `hasattr` existence. As a result, a client can set any public, existing view attribute — not just the fields actually bound with `dj-model=` in the rendered template. The denylist covers framework plumbing but nothing about developer business/authz state, and the allowlist is opt-in (off by default). A developer who binds one `dj-model="search"` input and also keeps `self.account_id` / `self.is_admin` / `self.total_price` as view state does not realize a client can set ALL of them via `{type:event, event:"update_model", params:{field, value}}` over the WebSocket. Type coercion matches the target attribute's type (so `"true"` -> bool True), aiding the attacker. This issue is fixed in djust 1.0.7. As a workaround, set `allowed_model_fields` explicitly on every view using dj-model (or subclassing LiveView) to the minimal list of bindable fields; do not keep authorization/ownership state in public view attributes that share the view with dj-model bindings.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.

## Package advisory (CVE-2026-61598)

Affected packages:

- `djust < 1.0.7`

Patched in:

- `djust 1.0.7`

Source: https://github.com/advisories/GHSA-cc7c-9jff-58wj