Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.1amended

djust has broken object-level access control (IDOR)

CVE-2026-61596GHSA-c7c5-5j6r-q957

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.

Add to your agent

Affected packages

  • PyPI djust

    Affected
    < 1.0.7
    Fixed in
    1.0.7

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
EPSS
  • CVE-2026-61596: 0.33% estimated exploitation activity in the next 30 days; percentile 25.91 (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 per-object authorization (getobject + hasobjectpermission, ADR-017) was enforced on the WebSocket mount and event paths but not on three other render entry points: (a) the initial HTTP GET render, (b) SPA urlchange navigation, and (c) {% liverender %} embedded child views. An authenticated user could therefore view (and on some paths act on) an object they are not authorized for by loading the page directly, navigating to it via SPA url-change, or composing it as an embedded child — a classic IDOR / broken object-level access control on object-scoped views. Patches Fixed in djust 1.0.7. All render entry points now route through a shared enforceobjectpermission chokepoint: HTTP GET returns 403, urlchange emits a permissiondenied frame and skips the render, and {% liverender %} (eager + lazy) refuses the embed. Views without a custom getobject are unaffected (no-op). Workarounds No reliable workaround short of upgrading. Do not expose object-scoped views through the…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-c7c5-5j6r-q957

  2. Revision 2 · amended ·

    Amended from osv record GHSA-c7c5-5j6r-q957

  3. Revision 1 · created ·

    Published from ghsa record GHSA-c7c5-5j6r-q957

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-61596

Advisory: djust has broken object-level access control (IDOR)
IDs: CVE-2026-61596, GHSA-c7c5-5j6r-q957
Record: https://patchnext.com/advisories/cve-2026-61596 (revision 3, source checked 26 Oct 2026, 13:52 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
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-c7c5-5j6r-q957 (GitHub-reviewed advisory GHSA-c7c5-5j6r-q957 lists affected ranges: PyPI djust >=0 <1.0.7)
- Verified: https://osv.dev/vulnerability/GHSA-c7c5-5j6r-q957 (OSV record GHSA-c7c5-5j6r-q957 lists affected ranges: PyPI djust >=0 <1.0.7 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…