Skip to main content
VulnerabilityPublished Updated

CVE-2026-61599: djust has an unauthenticated arbitrary module import via the WebSocket/SSE view-mount path

Affects djustSource GCVE Database

0
Compare
Authoritative record:CVE-2026-61599· High 8.8

Not known to be exploited · CVSS 8.8 High : upgrade to 1.0.7 soon.

Data as of 6 Nov 2026, 01:04 UTC

CVSS 4.0 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 1.0.7
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade djust to 1.0.7.

Affected software

ProductAffectedFixed in
PyPIdjustAffected
  • <1.0.7
Fixed in
  • 1.0.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in djust version 1.0.7 that fixes the vulnerability by enforcing a fail-closed import allowlist and restricting imports to already loaded modules or explicitly allowed modules. Users should upgrade to version 1.0.7 or later. As a workaround before patching, set LIVEVIEW_ALLOWED_MODULES to a narrow list of modules containing mountable LiveView classes, though this is only a mitigation and not a complete fix.

Description

The djust framework has an unauthenticated arbitrary module import vulnerability (CVE-2026-61599) in its WebSocket/SSE view-mount path. An unauthenticated client can specify any importable Python module path, causing the server to import and execute the module's top-level code before any authentication or subclass checks occur. This leads to potential remote code execution by proxy, denial of service, and module enumeration. The issue is fixed in version 1.0.7 by enforcing a fail-closed import allowlist and restricting imports to already loaded modules or explicitly allowed modules.

References

Community reviews

Loading reviews…