PT-2026-106735

CVE-2026-87975

·

Published

2026-10-06

·

Updated

2026-10-28

Description by

CVSS 4.0
5.3
Medium
MetricsAV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Name of the Vulnerable Software and Affected Versions Django versions prior to 6.1.2 Django versions prior to 6.0.9 Django versions prior to 5.2.18
Description An issue exists in the save existing objects() function within django.forms.models.BaseModelFormSet. The function incorrectly uses the presence of a primary key on a submitted form instance to verify if the instance belongs to the formset's limiting queryset. When a model's primary key is a field accepted by the form—such as a OneToOneField, a parent link in an inline formset, or a natural/UUID primary key—an authenticated user can populate the primary key via submitted data. This allows a user to delete rows outside the limiting queryset by forging management-form data, even without permissions for the targeted object. Models using the default AutoField primary key are not affected.
Recommendations Update to version 6.1.2 or newer. Update to version 6.0.9 or newer. Update to version 5.2.18 or newer.
Exploitability
Exploit
Fix
Impacts
Vendors
Affected products
Related identifiers
OPENSUSE-SU-2026:12086-1
OPENSUSE-SU-2026:12095-1
OPENSUSE-SU-2026:12103-1
OPENSUSE-SU-2026:22196-1
SUSE-SU-2026:4626-1
Found an issue in the description? Have something to add? Feel free to write us 👾