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

Back
New CVE Detected

CVE-2026-61594 – Authorization Bypass (WebSocket/SSE) – djust < 1.0.7

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-61594 is a critical authorization bypass vulnerability in djust, a Django library that provides Phoenix LiveView-style reactive server-side rendering. Versions prior to 1.0.7 authorize live WebSocket/SSE view mounts using a separate code path (check_view_auth) rather than Django’s standard View.dispatch() chain, allowing anonymous or under-privileged users to bypass LoginRequiredMixin, PermissionRequiredMixin, and UserPassesTestMixin protections when connecting over the live transport. The issue carries a CVSS v3.1 base score of 9.1 (Critical) and can expose restricted views and admin-level functionality to unauthenticated attackers over the network.

Technical details

  • Root cause: djust’s live (WebSocket) transport enforces authorization through its own check_view_auth mechanism instead of routing requests through Django’s standard View.dispatch() chain, creating an inconsistency between HTTP and WebSocket/SSE enforcement paths.
  • Trigger conditions: A view relies solely on standard Django authorization mixins/decorators (e.g., LoginRequiredMixin, PermissionRequiredMixin, UserPassesTestMixin) that are only evaluated during the initial HTTP GET request, while the same view is also mounted over djust’s live WebSocket/SSE transport.
  • Attack vector: Network — an attacker establishes a WebSocket/SSE connection directly to a protected LiveView mount, without needing to authenticate via the normal HTTP flow, since Django’s dispatch-based authorization is not re-applied on that transport.
  • Impact: Confidentiality and integrity are both rated High — attackers can view and interact with restricted view state and functionality, including admin operations, without valid credentials. Availability is not impacted (A:N).

Affected software

  • djust (djust-org/djust) versions prior to 1.0.7

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
  • Associated weaknesses: CWE-306 (Missing Authentication for Critical Function), CWE-862 (Missing Authorization)

Mitigation and recommended actions

  • Immediate: Upgrade djust to version 1.0.7 or later, which enforces authorization consistently across HTTP and live WebSocket/SSE transports.
  • If immediate patching is not possible: Do not rely solely on standard HTTP-only Django authorization patterns (LoginRequiredMixin, PermissionRequiredMixin, UserPassesTestMixin) for LiveViews exposed over djust’s live transport. Instead, explicitly apply djust’s transport-agnostic security attributes (login_required, permission_required, check_permissions) to every LiveView that must be protected, and audit existing LiveViews to confirm access controls are enforced on the WebSocket/SSE mount path, not just the initial HTTP request.

References

Are you exposed?

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge