{"answers":{"affected":"3 open source packages ship an affected version, including djust.","exploited":"There is no known exploitation of CVE-2026-61595 in the wild and no public exploit code.","fix":"Upgrade djust to 1.0.7 or later.","what":"CVE-2026-61595 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-61595 and fix it if it is affected.\n\nWhat it is: CVE-2026-61595 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-61595 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-61595/ (Markdown: https://insights.sbomify.com/CVE-2026-61595/index.md)","id":"CVE-2026-61595","markdown":"https://insights.sbomify.com/CVE-2026-61595/index.md","name":"CVE-2026-61595","record":{"aliases":["GHSA-3492-cvg7-9mr2","PYSEC-2026-4036"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Django reactive rendering library","requires_auth":"low_privilege","summary":"Attackers can access other tenants' data via WebSocket/SSE connections due to failed tenant isolation in the djust library.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-636","name":"Not Failing Securely"}],"description":"djust provides Phoenix LiveView-style reactive server-side rendering for Django with Rust-powered performance. Prior to version 1.0.7, `djust.tenants` isolation was enforced only on the HTTP path. The current tenant was stored in `threading.local()` and set exclusively by the HTTP-only `TenantMiddleware`, so on the live (WebSocket/SSE) path `get_current_tenant()` was always `None` during mount and every event handler — and the tenant-aware `QuerySet` manager failed OPEN (returned the unfiltered queryset, ignoring `STRICT_MODE`), disclosing every tenant's rows to whoever held the socket. `threading.local` was additionally shared across connections on the `sync_to_async` executor thread. This issue is fixed in djust 1.0.7. Tenant storage moved to a `contextvars.ContextVar` (per async task); the resolved tenant is bound around WS/SSE mount and every dispatch; both managers scope the base queryset once and fail CLOSED (`.none()` under the default `STRICT_MODE`); and system check S006 warns when `STRICT_MODE=False`. No known workarounds are available on the live path.","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: Multi-tenant isolation fails open on the WebSocket/SSE path, disclosing other tenants' data","id":"CVE-2026-61595","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 has broken object-level access control (IDOR)","id":"CVE-2026-61596"},"packages":[{"ecosystem":"PyPI","fixed":["1.0.7"],"introduced":["0"],"last_affected":[],"package":"djust","purl":null,"source":"GHSA-3492-cvg7-9mr2"},{"ecosystem":"PyPI","fixed":["1.0.7"],"introduced":["0"],"last_affected":[],"package":"djust","purl":"pkg:pypi/djust","source":"GHSA-3492-cvg7-9mr2"},{"ecosystem":"PyPI","fixed":["1.0.7"],"introduced":["0"],"last_affected":[],"package":"djust","purl":"pkg:pypi/djust","source":"PYSEC-2026-4036"}],"prev":{"headline":"djust has an authorization bypass on the WebSocket/SSE mount path","id":"CVE-2026-61594"},"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-16","vendors":["djust-org"]},"summary":"Attackers can access other tenants' data via WebSocket/SSE connections due to failed tenant isolation in the djust library.","url":"https://insights.sbomify.com/CVE-2026-61595/"}