Bug 2547359

Summary: CVE-2026-87975 python-django4.2: Privilege abuse in model formsets with editable primary keys [epel-all]
Product: [Fedora] Fedora EPEL Reporter: Vladimir Vasilev <vvasilev>
Component: python-django4.2Assignee: Michel Lind <michel>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: epel10CC: michel, python-packagers-sig
Target Milestone: ---Keywords: Security, SecurityTracking
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: {"flaws": ["2d4e61c1-0d0e-487d-8f30-017bed7b527f"]}
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2544152    

Description Vladimir Vasilev 2026-10-07 10:26:48 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

A flaw was found in Django. Model formsets did not correctly validate primary key values submitted in forged POST data when a model's primary key could be set through the form itself, such as with a OneToOneField (or a parent link used as the primary key of an inline formset's model), or a natural or UUID primary key included among the form's fields. An attacker with access to submit data to such a formset could forge POST data referencing primary keys outside the formset's limiting queryset, causing the formset to delete instances outside that queryset, or create instances through what was intended to be an edit-only formset. Models using the default BigAutoField primary key are not affected, since the primary key is not attacker-settable through the form.