{"answers":{"affected":"3 open source packages ship an affected version, including djust.","exploited":"There is no known exploitation of CVE-2026-61596 in the wild and no public exploit code.","fix":"Upgrade djust to 1.0.7 or later.","what":"CVE-2026-61596 is a high-severity missing authorization vulnerability in djust-org djust, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-61596 and fix it if it is affected.\n\nWhat it is: CVE-2026-61596 is a high-severity missing authorization vulnerability in djust-org djust, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-61596 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- djust (PyPI): affected all versions; fixed in 1.0.7\n- djust (PyPI): affected all versions; fixed in 1.0.7\n- djust (PyPI): affected all versions; fixed in 1.0.7\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-61596/ (Markdown: https://insights.sbomify.com/CVE-2026-61596/index.md)","id":"CVE-2026-61596","markdown":"https://insights.sbomify.com/CVE-2026-61596/index.md","name":"CVE-2026-61596","record":{"aliases":["GHSA-c7c5-5j6r-q957","PYSEC-2026-4041"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Django reactive rendering library","requires_auth":"low_privilege","summary":"Authenticated attackers can bypass object-level authorization to view or modify unauthorized data via specific render entry points in djust.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"djust provides Phoenix LiveView-style reactive server-side rendering for Django with Rust-powered performance. Prior to version 1.0.7, djust's per-object authorization (`get_object` + `has_object_permission`, 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 `url_change` navigation, and (c) `{% live_render %}` 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. This is fixed in djust 1.0.7. All render entry points now route through a shared `enforce_object_permission` chokepoint: HTTP GET returns 403, `url_change` emits a `permission_denied` frame and skips the render, and `{% live_render %}` (eager + lazy) refuses the embed. Views without a custom `get_object` are unaffected (no-op). No reliable workaround short of upgrading. Do not expose object-scoped views through the HTTP-GET / url_change / live_render paths until patched.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"djust has broken object-level access control (IDOR)","id":"CVE-2026-61596","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"djust is vulnerable to stored/reflected XSS via javascript: URLs in built-in component template tags","id":"CVE-2026-61597"},"packages":[{"ecosystem":"PyPI","fixed":["1.0.7"],"introduced":["0"],"last_affected":[],"package":"djust","purl":null,"source":"GHSA-c7c5-5j6r-q957"},{"ecosystem":"PyPI","fixed":["1.0.7"],"introduced":["0"],"last_affected":[],"package":"djust","purl":"pkg:pypi/djust","source":"GHSA-c7c5-5j6r-q957"},{"ecosystem":"PyPI","fixed":["1.0.7"],"introduced":["0"],"last_affected":[],"package":"djust","purl":"pkg:pypi/djust","source":"PYSEC-2026-4041"}],"prev":{"headline":"djust: Multi-tenant isolation fails open on the WebSocket/SSE path, disclosing other tenants' data","id":"CVE-2026-61595"},"products":["djust"],"published":"2026-09-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-17","vendors":["djust-org"]},"summary":"Authenticated attackers can bypass object-level authorization to view or modify unauthorized data via specific render entry points in djust.","url":"https://insights.sbomify.com/CVE-2026-61596/"}