{"answers":{"affected":"3 open source packages ship an affected version, including djust.","exploited":"There is no known exploitation of CVE-2026-61588 in the wild and no public exploit code.","fix":"Upgrade djust to 1.0.7 or later.","what":"CVE-2026-61588 is a medium-severity 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-61588 and fix it if it is affected.\n\nWhat it is: CVE-2026-61588 is a medium-severity 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-61588 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-61588/ (Markdown: https://insights.sbomify.com/CVE-2026-61588/index.md)","id":"CVE-2026-61588","markdown":"https://insights.sbomify.com/CVE-2026-61588/index.md","name":"CVE-2026-61588","record":{"aliases":["GHSA-pvg3-6q9j-mj3x","PYSEC-2026-4045"],"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":"djust library leaks sensitive model fields like password hashes and PII to clients when models are assigned to public view attributes.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-359","name":"Exposure of Private Personal Information to an Unauthorized Actor"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"djust provides Phoenix LiveView-style reactive server-side rendering for Django with Rust-powered performance. Prior to version 1.0.7, when a Django `Model` instance is assigned to a public view attribute, djust serialized it to the client with no sensitive-field denylist — sending fields such as `password` (the hash), privilege flags (e.g. `is_staff` / `is_superuser`), tokens, and other PII to the browser. Because exposing model objects to templates is a normal djust pattern, this could leak credentials/PII without the developer realizing the full object crossed the wire. This is fixed in djust 1.0.7. Model serialization applies a secure-by-default sensitive-field denylist (password/hash/token/secret-style fields and known privilege flags are withheld) with an identity-subset fallback. As a workaround, keep `Model` instances on `_private` attributes and expose only the specific fields needed, 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's Django model serialization has no sensitive-field denylist: password hashes, privilege flags, and PII on a public view attribute are sent to the client","id":"CVE-2026-61588","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":3,"n_references":2,"next":{"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"},"packages":[{"ecosystem":"PyPI","fixed":["1.0.7"],"introduced":["0"],"last_affected":[],"package":"djust","purl":null,"source":"GHSA-pvg3-6q9j-mj3x"},{"ecosystem":"PyPI","fixed":["1.0.7"],"introduced":["0"],"last_affected":[],"package":"djust","purl":"pkg:pypi/djust","source":"GHSA-pvg3-6q9j-mj3x"},{"ecosystem":"PyPI","fixed":["1.0.7"],"introduced":["0"],"last_affected":[],"package":"djust","purl":"pkg:pypi/djust","source":"PYSEC-2026-4045"}],"prev":{"headline":"Lightdash: Unauthenticated dbt Cloud webhook with path injection leaks API key","id":"CVE-2026-61576"},"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-19","vendors":["djust-org"]},"summary":"djust library leaks sensitive model fields like password hashes and PII to clients when models are assigned to public view attributes.","url":"https://insights.sbomify.com/CVE-2026-61588/"}