Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-pg97-jvmf-qfvc

djust has Cross-Site Request Forgery on the Server-Sent-Events transport: a cross-origin page can drive a victim-authenticated SSE session

CVSS 8.1 HighEPSS 0.0021 · 11th percentile

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

PackageEcosystemAffectedFixed in
djustPyPI<1.0.71.0.7
Identifiers
GHSA-pg97-jvmf-qfvc · CVE-2026-61593 · PYSEC-2026-4044
Weakness (CWE)
CWE-352
Tags
Published
16 Sept 2026
Updated
1 Oct 2026

Machine-written summary

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

The djust package, versions before 1.0.7, has a cross-site request forgery flaw in its Server-Sent Events transport. A cross-origin web page can make a victim's browser open an SSE session and send events that run state-changing handlers as the logged-in victim, with no Origin check or CSRF protection on those endpoints. Upgrade to djust 1.0.7, which checks request Origin against ALLOWED_HOSTS and requires JSON content type on POST requests. Until then, disable the SSE transport or place it behind a proxy that enforces an Origin allowlist.

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

ScoreRatingCVSSVectorSource
8.1 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0021, the 11th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:09 UTC First seen by agentprime
  2. 31 Oct 2026, 14:09 UTC Confirmed by OSV

Sources

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.