Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-61599Published 2026-09-16

CVE-2026-61599 — djust-org djust

high (derived)

As of 2026-09-17, CVE-2026-61599 is a High-severity (band derived from the CVSS v4.0 score, not stated by the CNA) vulnerability in djust-org djust, CVSS v4.0 8.8. No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-61599 as of 2026-09-17; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v4.0
8.8/10High (derived)
EPSS
—No EPSS score yet
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
4.4/10Threadlinqs triage score
Published
Updated 2026-09-17
CVSS v4.0 8.8 (High, derived from score) · Priority 4.4/10 · Published 2026-09-16

Last updated:

What is CVE-2026-61599?

djust provides Phoenix LiveView-style reactive server-side rendering for Django with Rust-powered performance. Prior to version 1.0.7, the djust live transport resolves the LiveView to mount from a client-supplied dotted path by calling `__import__(module_path, ...)`. The module is imported — running its top-level code (import side effects) — before the framework checks that the resolved object is a `LiveView` subclass and before any per-view authentication. The `LIVEVIEW_ALLOWED_MODULES` allowlist that should contain this is fail-open (`if allowed_modules:` — skipped when the setting is unset, the framework default) and uses loose `startswith` matching. An unauthenticated WebSocket client (the WS handshake does not require auth; per-view auth runs only after import + instantiate) can therefore send a `mount` / `live_redirect_mount` / `url_change` frame (or an SSE mount) with `view = ".AnyName"` and cause the server to import — and execute the top-level code of — any importable Python module by name. Version 1.0.7 fixes the issue with a fail-closed resolution gate (`djust._view_resolution.is_view_import_allowed`): a client view path resolves only if (a) its module is already loaded (`sys.modules` — so resolving runs no new code; URL-routed views loaded by URLconf at startup keep working with zero config) or (b) it matches `LIVEVIEW_ALLOWED_MODULES` on a module-segment boundary (explicit opt-in for lazily-imported views). The gate runs before `__import__` at all three sinks (+ defense-in-depth inside `_instantiate_view`). As a workaround, set `LIVEVIEW_ALLOWED_MODULES` to the narrow list of modules that contain your mountable LiveView classes. (Note: pre-patch the allowlist is `startswith`-matched and the import still precedes the subclass check, so this is mitigation, not a complete fix.)

The record classifies CVE-2026-61599 under weakness class CWE-470. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 64 days ago.

Severity and exploitation probability

CVSS v4.0 base score
8.8 — High (derived from score)
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
4.4/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-09-16

Is CVE-2026-61599 being exploited?

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

Affected products and versions

  • djust-org: djust

Affected software packages:

  • pip:djust — patched in 1.0.7

How to fix CVE-2026-61599

Fixed versions are recorded for 1 package: pip:djust 1.0.7. No vendor patch reference has been recorded for CVE-2026-61599 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-61599

No threat campaign in the Threadlinqs corpus currently references CVE-2026-61599, 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, GitHub Security Advisories. This product uses the NVD API but is not endorsed or certified by the NVD.

Vendor advisory and patch

Other references