# djust authentication bypass: a login_required / on_mount LiveView mount redirect does not close the WebSocket, allowing an unauthenticated client to dispatch event-handler calls

Advisory record · `GHSA-xx4j-w367-7247`

- **Identifiers:** `GHSA-xx4j-w367-7247` · `CVE-2026-55571` · `PYSEC-2026-3829`
- **State:** Confirmed
- **Severity:** CVSS 8.2 High
- **Critical:** No
- **Weakness (CWE):** [CWE-285](https://cwe.mitre.org/data/definitions/285.html) · [CWE-306](https://cwe.mitre.org/data/definitions/306.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md) · [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 25 Aug 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 25 Aug 2026, 16:06 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `djust` (PyPI): affected `<1.0.4`; fixed in `1.0.4`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> GHSA-xx4j-w367-7247: djust versions below 1.0.4 do not close the WebSocket after a login_required, permission_required, or redirecting on_mount hook sends an auth redirect on a LiveView mount. A raw WebSocket client that ignores the redirect can keep the socket open and send event frames to invoke event handlers on the gated view without an authenticated session. Upgrade to djust 1.0.4, which closes the socket after the redirect. If you cannot upgrade, make sure each event handler on gated views checks that the user is authenticated and authorized.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.2 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0050, the 43rd percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:10 UTC: First seen by agentprime
- 31 Oct 2026, 14:10 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-xx4j-w367-7247)

## Sources

- [GitHub Advisory Database: GHSA-xx4j-w367-7247](https://github.com/advisories/GHSA-xx4j-w367-7247)
- [OSV: GHSA-xx4j-w367-7247](https://osv.dev/vulnerability/GHSA-xx4j-w367-7247)
- <https://github.com/djust-org/djust/security/advisories/GHSA-xx4j-w367-7247>
- <https://github.com/djust-org/djust/pull/1780>
- <https://github.com/djust-org/djust/commit/1ae8aa9246b80477de7ddc4d90319a3b267bef04>
- <https://github.com/djust-org/djust>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-xx4j-w367-7247>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-xx4j-w367-7247/>. Everything for agents: <https://agentprime.io/llms.txt>.