djust provides Phoenix LiveView-style reactive server-side rendering for Django with Rust-powered performance. Prior to version 1.0.7, SSE sessions were keyed solely by a client-chosen session_id with no binding to the authenticated user — a control the WebSocket transport has but that was dropped on SSE. An attacker who learns (or a victim who leaks) a session_id could connect to the message endpoint and dispatch event handlers that execute with the victim's identity and state. This is fixed in djust 1.0.7. Each SSE session is bound to its owning principal at creation and cross-principal access is rejected; SSE session creation is additionally capped per principal. As a workaround, disable the SSE transport.
CVE-2026-61592
This high-severity CVE scores 7.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 78% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.4
- EG Score
- 7.4(medium)
- EG Risk
- 33(Track)EG Risk 33/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity74% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 22%
- KEV
- Not listed
Published
September 16, 2026
Last Modified
September 17, 2026
Advisory Details (2)
Auto-updated Sep 16, 2026SSE sessions are not bound to the authenticated user; the client-chosen session_id is the sole authorization capability (session hijack) · Advisory · djust-org/djust · GitHub
https://github.com/djust-org/djust/security/advisories/GHSA-f795-p5jw-j6g2v1.0.7
Patch available: djust-org/djust v1.0.7
https://github.com/djust-org/djust/releases/tag/v1.0.7Vendor Advisories for CVE-2026-61592(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| djust | 0.1.0 ... 1.0.6 (68 versions) | 1.0.7 | — |
Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-19 05:15 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 20:18 UTCEG score recompute
- 2026-09-17 19:31 UTCEG score recompute
- 2026-09-16 22:25 UTCEG score recompute
- 2026-09-16 21:54 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-862 · CWE-384
Frequently asked(5)
What is CVE-2026-61592?
When was CVE-2026-61592 disclosed?
Is CVE-2026-61592 actively exploited?
What is the CVSS score of CVE-2026-61592?
How do I remediate CVE-2026-61592?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-61592
Is Your Infrastructure Affected by CVE-2026-61592?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.