# CVE-2026-61596 — djust-org djust

> As of 2026-09-17, CVE-2026-61596 is a HIGH-severity vulnerability in djust-org djust, CVSS v3.1 7.1. No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-61596 as of 2026-09-17; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-09-17

## What is CVE-2026-61596?

djust provides Phoenix LiveView-style reactive server-side rendering for Django with Rust-powered performance. Prior to version 1.0.7, djust's per-object authorization (`get_object` + `has_object_permission`, ADR-017) was enforced on the WebSocket mount and event paths but not on three other render entry points: (a) the initial HTTP GET render, (b) SPA `url_change` navigation, and (c) `{% live_render %}` embedded child views. An authenticated user could therefore view (and on some paths act on) an object they are not authorized for by loading the page directly, navigating to it via SPA url-change, or composing it as an embedded child — a classic IDOR / broken object-level access control on object-scoped views. This is fixed in djust 1.0.7. All render entry points now route through a shared `enforce_object_permission` chokepoint: HTTP GET returns 403, `url_change` emits a `permission_denied` frame and skips the render, and `{% live_render %}` (eager + lazy) refuses the embed. Views without a custom `get_object` are unaffected (no-op). No reliable workaround short of upgrading. Do not expose object-scoped views through the HTTP-GET / url_change / live_render paths until patched.

The record classifies CVE-2026-61596 under weakness classes [CWE-639](https://intel.threadlinqs.com/cwe/CWE-639), [CWE-862](https://intel.threadlinqs.com/cwe/CWE-862). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs low-privilege credentials, needs no user interaction, and has high impact on confidentiality. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 19 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 7.1 — HIGH (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N`)
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 3.6/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-09-16, last modified 2026-09-17

## Is CVE-2026-61596 being exploited?

It currently carries a trending score of 30 in the Threadlinqs vulnerability feed.

## Affected products and versions

- **djust-org**: djust

## How to fix CVE-2026-61596

No vendor patch reference has been recorded for CVE-2026-61596 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-61596

No threat campaign in the Threadlinqs corpus currently references CVE-2026-61596, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD. Last verified by Threadlinqs on 2026-09-17. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [github.com](https://github.com/djust-org/djust/security/advisories/GHSA-c7c5-5j6r-q957)

**Other references**

- [github.com](https://github.com/djust-org/djust/releases/tag/v1.0.7)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-61596
Full detection coverage and IOCs for threats exploiting CVE-2026-61596 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp