{"answers":{"affected":"3 open source packages ship an affected version, including djust.","exploited":"There is no known exploitation of CVE-2026-61590 in the wild and no public exploit code.","fix":"Upgrade djust to 1.0.7 or later.","what":"CVE-2026-61590 is a high-severity missing authorization vulnerability in djust-org djust, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-61590 and fix it if it is affected.\n\nWhat it is: CVE-2026-61590 is a high-severity missing authorization vulnerability in djust-org djust, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-61590 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-61590/ (Markdown: https://insights.sbomify.com/CVE-2026-61590/index.md)","id":"CVE-2026-61590","markdown":"https://insights.sbomify.com/CVE-2026-61590/index.md","name":"CVE-2026-61590","record":{"aliases":["GHSA-8g2f-g3gq-5rjv","PYSEC-2026-4039"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Django reactive rendering library","requires_auth":"none","summary":"Attackers can read live application state and execute remote code via exposed observability endpoints if the optional localhost middleware is omitted and DEBUG is enabled.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-668","name":"Exposure of Resource to Wrong Sphere"},{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"djust provides Phoenix LiveView-style reactive server-side rendering for Django with Rust-powered performance. Prior to version 1.0.7, djust's observability endpoints expose live view/session state and a remote method-invocation surface (`eval_handler`). 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. This issue is 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 `eval_handler` is restricted; gated requests receive a non-disclosing response. As a workaround, ensure `DEBUG=False` in production, and do not expose the observability endpoints to untrusted networks.","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's observability endpoints are network-exposed: the localhost gate is an opt-in middleware the docs omit, and the views enforce only DEBUG","id":"CVE-2026-61590","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: Unsigned client state snapshot is restored as trusted view state (privilege escalation / state injection)","id":"CVE-2026-61591"},"packages":[{"ecosystem":"PyPI","fixed":["1.0.7"],"introduced":["0"],"last_affected":[],"package":"djust","purl":null,"source":"GHSA-8g2f-g3gq-5rjv"},{"ecosystem":"PyPI","fixed":["1.0.7"],"introduced":["0"],"last_affected":[],"package":"djust","purl":"pkg:pypi/djust","source":"GHSA-8g2f-g3gq-5rjv"},{"ecosystem":"PyPI","fixed":["1.0.7"],"introduced":["0"],"last_affected":[],"package":"djust","purl":"pkg:pypi/djust","source":"PYSEC-2026-4039"}],"prev":{"headline":"djust: WebSocket/runtime reconstructed request omits the client Host, causing host/subdomain TenantResolvers to misresolve the tenant on the live path","id":"CVE-2026-61589"},"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":"total"},"state":"PUBLISHED","updated":"2026-09-16","vendors":["djust-org"]},"summary":"Attackers can read live application state and execute remote code via exposed observability endpoints if the optional localhost middleware is omitted and DEBUG is enabled.","url":"https://insights.sbomify.com/CVE-2026-61590/"}