{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-87975 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-87975 is a medium-severity missing authorization vulnerability in djangoproject Django, published on 6 Oct 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-87975 and fix it if it is affected.\n\nWhat it is: CVE-2026-87975 is a medium-severity missing authorization vulnerability in djangoproject Django, published on 6 Oct 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-87975 in the wild and no public exploit code.\n\nAffected product: djangoproject Django. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-87975/ (Markdown: https://insights.sbomify.com/CVE-2026-87975/index.md)","id":"CVE-2026-87975","markdown":"https://insights.sbomify.com/CVE-2026-87975/index.md","name":"CVE-2026-87975","record":{"aliases":["DEBIAN-CVE-2026-87975","GHSA-x869-hccf-fv7r","UBUNTU-CVE-2026-87975"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Django web framework","requires_auth":"low_privilege","summary":"Authenticated users can delete unauthorized database rows by exploiting editable primary keys in Django model formsets.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"DSF","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"An issue was discovered in Django 6.1 before 6.1.2, 6.0 before 6.0.9, and 5.2 before 5.2.18.\n`django.forms.models.BaseModelFormSet.save_existing_objects()` used the presence of a primary key on a submitted form's instance as evidence that the instance belonged to the formset's limiting queryset. An object outside that queryset is represented by a newly constructed instance whose primary key can still be populated from submitted data when the model's primary key is a field accepted by the form, such as a `OneToOneField` or parent link used as the primary key of an inline formset's model, or a natural or UUID primary key included in the form's fields. This allows an authenticated user permitted to submit such a formset to delete rows outside the limiting queryset, without any permission on the targeted object, via forged management-form data marking an out-of-queryset object for deletion. Models using the default AutoField primary key are not affected.\nEarlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected.\nDjango would like to thank Seonggwon Yoon for reporting this issue.","ecosystems":[],"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":"Privilege abuse in model formsets with editable primary keys","id":"CVE-2026-87975","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"Apache NiFi Registry: Improper Limitation of Pathname in Persisted Extension Bundles","id":"CVE-2026-87976"},"packages":[],"prev":{"headline":"Asaas Gateway for WooCommerce \u003c 2.7.8 - Unauthenticated Order Payment Bypass via Webhook","id":"CVE-2026-87974"},"products":["Django"],"published":"2026-10-06","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-10-06","vendors":["djangoproject"]},"summary":"Authenticated users can delete unauthorized database rows by exploiting editable primary keys in Django model formsets.","url":"https://insights.sbomify.com/CVE-2026-87975/"}