# djust has an authorization bypass on the WebSocket/SSE mount path

Advisory record · `GHSA-xhhm-f6hp-2qwj`

- **Identifiers:** `GHSA-xhhm-f6hp-2qwj` · `CVE-2026-61594` · `PYSEC-2026-4047`
- **State:** Confirmed
- **Severity:** CVSS 9.1 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-306](https://cwe.mitre.org/data/definitions/306.html) · [CWE-862](https://cwe.mitre.org/data/definitions/862.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md) · [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 16 Sept 2026
- **Updated:** 1 Oct 2026
- **Reviewed by a person:** No

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

## Critical

Critical, because:

- CVSS score 9.1: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

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

## Machine-written summary

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

> Versions of djust before 1.0.7 are affected. On the WebSocket/SSE mount path, Django authorization such as LoginRequiredMixin, PermissionRequiredMixin, and the djust admin staff gate is not enforced, though it is enforced on the HTTP GET. An anonymous or under-privileged client that can open a WebSocket can mount such views, including admin pages, and invoke their handlers. Upgrade to djust 1.0.7. Until then, protect views with djust's own login_required, permission_required, or check_permissions attributes, which apply on all transports.

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

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

- **CISA KEV:** Not listed.
- **EPSS:** 0.0049, the 42nd percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:09 UTC: First seen by agentprime
- 31 Oct 2026, 14:09 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-xhhm-f6hp-2qwj)

## Sources

- [GitHub Advisory Database: GHSA-xhhm-f6hp-2qwj](https://github.com/advisories/GHSA-xhhm-f6hp-2qwj)
- [OSV: GHSA-xhhm-f6hp-2qwj](https://osv.dev/vulnerability/GHSA-xhhm-f6hp-2qwj)
- <https://github.com/djust-org/djust/security/advisories/GHSA-xhhm-f6hp-2qwj>
- <https://github.com/djust-org/djust>
- <https://github.com/djust-org/djust/releases/tag/v1.0.7>

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-xhhm-f6hp-2qwj>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-xhhm-f6hp-2qwj/>. Everything for agents: <https://agentprime.io/llms.txt>.
