{"answers":{"affected":"3 open source packages ship an affected version, including django-unicorn. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-31815 exists.","fix":"Upgrade django-unicorn to 0.67.0 or later.","what":"CVE-2026-31815 is a medium-severity missing authorization vulnerability in django-commons django-unicorn, published on 10 Mar 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-31815 and fix it if it is affected.\n\nWhat it is: CVE-2026-31815 is a medium-severity missing authorization vulnerability in django-commons django-unicorn, published on 10 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-31815 exists.\n\nAffected packages and fixed versions:\n- django-unicorn (PyPI): affected all versions; fixed in 0.67.0\n- django-unicorn (PyPI): affected all versions; fixed in 0.67.0\n- django-unicorn (PyPI): affected all versions; fixed in 0.67.0\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-31815/ (Markdown: https://insights.sbomify.com/CVE-2026-31815/index.md)","id":"CVE-2026-31815","markdown":"https://insights.sbomify.com/CVE-2026-31815/index.md","name":"CVE-2026-31815","record":{"aliases":["GHSA-ffv6-jj46-x367","PYSEC-2026-2451"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Django reactive component library","requires_auth":"none","summary":"Attackers can bypass access controls to modify internal component attributes or trigger protected methods in django-unicorn.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"unicorn","vendor":"django-unicorn"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-915","name":"Improperly Controlled Modification of Dynamically-Determined Object Attributes"},{"id":"CWE-284","name":"Improper Access Control"}],"description":"Unicorn adds modern reactive component functionality to your Django templates. Prior to 0.67.0, component state manipulation is possible in django-unicorn due to missing access control checks during property updates and method calls. An attacker can bypass the intended _is_public protection to modify internal attributes such as template_name or trigger protected methods. This vulnerability is fixed in 0.67.0.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"django-unicorn affected by component state manipulation via unvalidated attribute access","id":"CVE-2026-31815","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"Budibase Universal Auth Bypass via Webhook Query Param Injection","id":"CVE-2026-31816"},"packages":[{"ecosystem":"PyPI","fixed":["0.67.0"],"introduced":["0"],"last_affected":[],"package":"django-unicorn","purl":null,"source":"GHSA-ffv6-jj46-x367"},{"ecosystem":"PyPI","fixed":["0.67.0"],"introduced":["0"],"last_affected":[],"package":"django-unicorn","purl":"pkg:pypi/django-unicorn","source":"GHSA-ffv6-jj46-x367"},{"ecosystem":"PyPI","fixed":["0.67.0"],"introduced":["0"],"last_affected":[],"package":"django-unicorn","purl":"pkg:pypi/django-unicorn","source":"PYSEC-2026-2451"}],"prev":{"headline":"Yamux remote Panic via malformed WindowUpdate credit","id":"CVE-2026-31814"},"products":["django-unicorn"],"published":"2026-03-10","related":[{"cvss_score":6.1,"headline":"Cross-site Scripting in django-unicorn","id":"CVE-2021-42134","kev_date_added":null,"published":"2021-10-11"},{"cvss_score":5.4,"headline":"Cross-site scripting in Unicorn framework","id":"CVE-2021-42053","kev_date_added":null,"published":"2021-10-07"}],"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":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-11","vendors":["django-commons"]},"summary":"Attackers can bypass access controls to modify internal component attributes or trigger protected methods in django-unicorn.","url":"https://insights.sbomify.com/CVE-2026-31815/"}