CVE-2026-87975
Deferred Deferred - Pending Action

Authentication Bypass in Django Formset Handling

Vulnerability report for CVE-2026-87975, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-06

Last updated on: 2026-10-06

Assigner: Django Software Foundation

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-06
Last Modified
2026-10-06
Generated
2026-10-06
AI Q&A
2026-10-06
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
djangoproject Django 6.1
djangoproject Django 6.0
djangoproject Django 5.2

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in Django versions before 6.1.2, 6.0.9, and 5.2.18 allows an authenticated user to delete database rows outside their permitted scope. It occurs because the formset handling logic incorrectly trusts primary key values submitted in forms, enabling manipulation of objects not included in the intended queryset. Models with non-default primary keys (like UUID or OneToOneField) are particularly affected.

Impact Analysis

If you use an affected Django version with models having non-default primary keys, an attacker with valid credentials could delete unauthorized records. This could lead to data loss, corruption of application state, or disruption of services relying on those records.

Mitigation Strategies

Upgrade Django to a patched version: 6.1.2 or later, 6.0.9 or later, or 5.2.18 or later. If using unsupported versions, consider upgrading to a supported release.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-87975. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart