Skip to content

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

HighCVSS 8.8 EPSS 0.60%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
No known exploitation · automatable: yes · technical impact: partial

Description

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 = "<any.importable.module>.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.)

Upgrade path

2 packages: 1 fixed.

PackageAffectedFixed inStatus
pypi djust(PyPI) < 1.0.7; = 0.1.0; = 0.1.2; = 0.1.3 +37 more 1.0.7 Fixed
djust-org djust = < 1.0.7 No fix listed Versions listed

Affected products

ProductAffected versionsFixed in
pypi djust(PyPI) < 1.0.7 1.0.7
pypi djust(PyPI) = 0.1.0 No fix listed
pypi djust(PyPI) = 0.1.2 No fix listed
pypi djust(PyPI) = 0.1.3 No fix listed
pypi djust(PyPI) = 0.1.4 No fix listed
pypi djust(PyPI) = 0.1.5 No fix listed
pypi djust(PyPI) = 0.1.6 No fix listed
pypi djust(PyPI) = 0.1.7 No fix listed
pypi djust(PyPI) = 0.1.8 No fix listed
pypi djust(PyPI) = 0.1.9 No fix listed
pypi djust(PyPI) = 0.2.0 No fix listed
pypi djust(PyPI) = 0.2.1 No fix listed
pypi djust(PyPI) = 0.2.2 No fix listed
pypi djust(PyPI) = 0.3.0 No fix listed
pypi djust(PyPI) = 0.3.1 No fix listed
pypi djust(PyPI) = 0.3.2 No fix listed
pypi djust(PyPI) = 0.3.4 No fix listed
pypi djust(PyPI) = 0.3.5 No fix listed
pypi djust(PyPI) = 0.3.6 No fix listed
pypi djust(PyPI) = 0.3.7 No fix listed
pypi djust(PyPI) = 0.3.8 No fix listed
pypi djust(PyPI) = 0.4.0 No fix listed
pypi djust(PyPI) = 0.4.1 No fix listed
pypi djust(PyPI) = 0.4.2 No fix listed
pypi djust(PyPI) = 0.4.3 No fix listed
Show 17 more
ProductAffected versionsFixed in
pypi djust(PyPI) = 0.4.4 No fix listed
pypi djust(PyPI) = 0.9.0 No fix listed
pypi djust(PyPI) = 0.9.1 No fix listed
pypi djust(PyPI) = 0.9.2 No fix listed
pypi djust(PyPI) = 0.9.4 No fix listed
pypi djust(PyPI) = 0.9.5 No fix listed
pypi djust(PyPI) = 0.9.6 No fix listed
pypi djust(PyPI) = 0.9.7 No fix listed
pypi djust(PyPI) = 1.0.0 No fix listed
pypi djust(PyPI) = 1.0.0rc11 No fix listed
pypi djust(PyPI) = 1.0.1 No fix listed
pypi djust(PyPI) = 1.0.2 No fix listed
pypi djust(PyPI) = 1.0.3 No fix listed
pypi djust(PyPI) = 1.0.4 No fix listed
pypi djust(PyPI) = 1.0.5 No fix listed
pypi djust(PyPI) = 1.0.6 No fix listed
djust-org djust = < 1.0.7 No fix listed

References