Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-61599 – Unauthenticated Remote Code Execution via Arbitrary Module Import – djust < 1.0.7

Be the first to know when new zero-days emerge:

Summary

CVE-2026-61599 is an unauthenticated arbitrary module import vulnerability in djust, a Django library that provides Phoenix LiveView-style reactive server-side rendering over WebSocket and Server-Sent Events (SSE). The framework resolves the LiveView component to mount by calling Python’s __import__ on a client-supplied dotted module path before any authentication check or verification that the resolved object is actually a LiveView subclass, allowing a remote, unauthenticated attacker to trigger execution of arbitrary Python module import-time code. The issue is rated High severity (CVSS 8.8) and affects all djust versions prior to 1.0.7.

Technical details

  • Root cause: djust’s mount-resolution logic accepts a client-supplied dotted module path over WebSocket or SSE and passes it directly to __import__() to locate the LiveView class to mount, executing that module’s top-level (import-time) code as a side effect.
  • Fail-open allowlist: The optional LIVEVIEW_ALLOWED_MODULES setting, intended to restrict which modules may be mounted, is skipped entirely when unset (the framework default), and even when configured it uses loose startswith prefix matching rather than exact module-boundary matching, making it bypassable.
  • Pre-authentication execution: The vulnerable import occurs before the framework verifies the resolved object is a genuine LiveView subclass and before any per-view authentication is enforced.
  • Attack surface: Three code paths are affected — handle_mount in websocket.py, ViewRuntime.dispatch_mount in runtime.py, and the SSE mount handlers in sse.py.
  • Attack vector / complexity: Network-exploitable, low attack complexity, no authentication or user interaction required.
  • Impact: Execution of arbitrary Python module code as a side effect of import, which can lead to remote code execution, information disclosure, or further compromise of the hosting application, depending on which importable modules are reachable in the server’s Python path.

Affected software

  • djust (djust-org) versions prior to 1.0.7

Severity

  • CVSS Score: 8.8 (High)
  • CVSS v4.0 Vector: 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
  • CWE-470: Use of Externally-Controlled Input to Select Classes or Code (Unsafe Reflection)

Mitigation and recommended actions

  • Immediate: Upgrade djust to version 1.0.7 or later, which introduces a fail-closed resolution gate that validates module imports against sys.modules or an explicit LIVEVIEW_ALLOWED_MODULES configuration before performing the import.
  • If immediate patching is not possible:
    • Explicitly configure LIVEVIEW_ALLOWED_MODULES to a narrow, precise list of modules that contain your mountable LiveView classes (note: on unpatched versions this control is bypassable via prefix matching and does not fully close the issue).
    • Restrict network exposure of WebSocket and SSE endpoints (e.g., via authentication at a reverse proxy or network-layer access controls) until the upgrade can be applied.
    • Monitor WebSocket/SSE mount requests for unexpected or unusual dotted module paths.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge