djust's observability endpoints are network-exposed: the localhost gate is an opt-in middleware the docs omit, and the views enforce only DEBUG
CVE-2026-61590GHSA-8g2f-g3gq-5rjv
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (djust 1.0.7), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI djust
- Affected
- < 1.0.7
- Fixed in
- 1.0.7
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-8g2f-g3gq-5rjv lists affected ranges: PyPI djust >=0 <1.0.7
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-8g2f-g3gq-5rjv lists affected ranges: PyPI djust >=0 <1.0.7 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 7.4 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
- EPSS
- CVE-2026-61590: 0.36% estimated exploitation activity in the next 30 days; percentile 29.41 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Impact djust's observability endpoints expose live view/session state and a remote method-invocation surface (evalhandler). The localhost restriction was an opt-in middleware that the documented setup omits; the views themselves enforced only DEBUG. In the misconfigured-but-documented scenario (DEBUG on, middleware not installed) a non-localhost client could read live application state and invoke handlers remotely. Patches Fixed in djust 1.0.7. The localhost restriction is enforced in-view on every observability endpoint (no longer dependent on a separately-installed middleware), and evalhandler is restricted; gated requests receive a non-disclosing response. Workarounds Ensure DEBUG=False in production, and do not expose the observability endpoints to untrusted networks.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-8g2f-g3gq-5rjv
- Revision 2 · amended ·
Amended from osv record GHSA-8g2f-g3gq-5rjv
- Revision 1 · created ·
Published from ghsa record GHSA-8g2f-g3gq-5rjv
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-61590 Advisory: djust's observability endpoints are network-exposed: the localhost gate is an opt-in middleware the docs omit, and the views enforce only DEBUG IDs: CVE-2026-61590, GHSA-8g2f-g3gq-5rjv Record: https://patchnext.com/advisories/cve-2026-61590 (revision 3, source checked 26 Oct 2026, 13:51 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.4) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: djust 1.0.7. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI djust: affected < 1.0.7; fixed in 1.0.7 ## Suggested inspection (read-only) - `python -m pip show djust`: prints the installed version. Run with the environment that serves production active. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on djust. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-8g2f-g3gq-5rjv (GitHub-reviewed advisory GHSA-8g2f-g3gq-5rjv lists affected ranges: PyPI djust >=0 <1.0.7) - Verified: https://osv.dev/vulnerability/GHSA-8g2f-g3gq-5rjv (OSV record GHSA-8g2f-g3gq-5rjv lists affected ranges: PyPI djust >=0 <1.0.7 (fixed)) Commands are suggestions: review each one before running it.
Loading voting…