CVE-2026-61592

HIGHPre-NVD 7.47.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.4 from GitHub Security Advisory (severity: HIGH) published 2026-09-16. A secondary CVSS source baseline 7.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-81301 (ENISA EUVD) · GHSA-f795-p5jw-j6g2 (GitHub Security Advisories) · PYSEC-2026-4043 (OSV.dev)Source: ENISA EUVD

7.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.4
EG Score
7.4HIGHmedium confidence
EG Risk
33
EG Risk 33/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity74% × 45%
Impact severity (EG Severity): CVSS 7.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
32nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.4): severity, escalated by confirmed exploitation. This CVE's 7.4 is its impact severity (EG Severity), not escalated.

EG Severity
7.4 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 16, 2026

Last Modified

September 30, 2026

Advisory Details (2)

Auto-updated Sep 16, 2026
Patch available. Sources: github_release, github.
GitHub advisoryMentions a patch (unverified)

SSE 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-j6g2
GitHub release Patch Available

v1.0.7

Patch available: djust-org/djust v1.0.7

https://github.com/djust-org/djust/releases/tag/v1.0.7

Vendor 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.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipdjust @ 1.0.7 (fixes < 1.0.7)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
djust0.1.0 ... 1.0.6 (40 versions)
  • every version up to 1.0.7: fixed in 1.0.7
—

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 49× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  2. 2026-11-01 07:41 UTCGHSA enrichmentGHSA-f795-p5jw-j6g2 · GitHub severity HIGH · GitHub CVSS 7.4
  3. 2026-11-01 07:41 UTCEG score recompute
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  5. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  6. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  7. 2026-10-29 02:53 UTCEG score recompute
  8. 2026-10-28 23:25 UTCOSV refresh
  9. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  10. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  11. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  12. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  13. 2026-10-25 14:14 UTCEG score recompute
  14. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  15. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  16. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  17. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  18. 2026-10-21 05:09 UTCEG score recompute
  19. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  20. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  21. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  22. 2026-10-18 03:25 UTCEG score recompute
  23. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  24. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  25. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
Show 51 more
  1. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  2. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  3. 2026-10-13 13:24 UTCEG score recompute
  4. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  5. 2026-10-12 15:50 UTCEG score recompute
  6. 2026-10-11 19:34 UTCEG score recompute
  7. 2026-10-11 16:49 UTCEG score recompute
  8. 2026-10-11 14:11 UTCEG score recompute
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  10. 2026-10-11 03:46 UTCEG score recompute
  11. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  12. 2026-10-10 03:04 UTCEG score recompute
  13. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  14. 2026-10-08 18:06 UTCEG score recompute
  15. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  16. 2026-10-08 02:20 UTCEG score recompute
  17. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  18. 2026-10-06 17:20 UTCEG score recompute
  19. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  20. 2026-10-05 19:23 UTCEG score recompute
  21. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  22. 2026-10-05 08:13 UTCEG score recompute
  23. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  24. 2026-10-03 23:13 UTCEG score recompute
  25. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  26. 2026-10-03 01:12 UTCEG score recompute
  27. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  28. 2026-10-02 03:11 UTCEG score recompute
  29. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  30. 2026-09-30 16:55 UTCEG score recompute
  31. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  32. 2026-09-29 18:24 UTCEG score recompute
  33. 2026-09-29 07:24 UTCEG score recompute
  34. 2026-09-27 22:27 UTCEG score recompute
  35. 2026-09-27 00:19 UTCEG score recompute
  36. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  37. 2026-09-26 02:13 UTCEG score recompute
  38. 2026-09-24 17:10 UTCEG score recompute
  39. 2026-09-23 19:12 UTCEG score recompute
  40. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  41. 2026-09-22 21:09 UTCEG score recompute
  42. 2026-09-21 23:11 UTCEG score recompute
  43. 2026-09-21 01:13 UTCEG score recompute
  44. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  45. 2026-09-19 16:14 UTCEG score recompute
  46. 2026-09-19 05:15 UTCEG score recompute
  47. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  48. 2026-09-17 20:18 UTCEG score recompute
  49. 2026-09-17 19:31 UTCEG score recompute
  50. 2026-09-16 22:25 UTCEG score recompute
  51. 2026-09-16 21:54 UTCEG score recomputeFirst assessed: 7.4 HIGH

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-61592?
CVE-2026-61592 is a high-severity vulnerability; its CVE record was published on September 16, 2026. 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…
When was the CVE record for CVE-2026-61592 published?
The CVE record for CVE-2026-61592 was published on September 16, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-61592 actively exploited?
CVE-2026-61592 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61592?
CVE-2026-61592 has a CVSS base score of 7.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-61592?
A fix for CVE-2026-61592 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-61592 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-61592

Explore →

Is Your Infrastructure Affected by CVE-2026-61592?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs