Bug 2547358

Summary:	CVE-2026-87975 python-django6: Privilege abuse in model formsets with editable primary keys [fedora-all]
Product:	[Fedora] Fedora	Reporter:	Vladimir Vasilev <vvasilev>
Component:	python-django6	Assignee:	Michel Lind <michel>
Status:	CLOSED ERRATA	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	infra-sig, michel, ngompa13, python-packagers-sig
Target Milestone:	---	Keywords:	Security, SecurityTracking
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	{"flaws": ["2d4e61c1-0d0e-487d-8f30-017bed7b527f"]}
Fixed In Version:	python-django6-6.1.2-1.fc44	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2026-10-17 01:05:12 UTC	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:39 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.

Comment 1 Fedora Update System 2026-10-08 10:18:43 UTC

FEDORA-2026-c221dbc190 (python-django6-6.1.2-1.fc45) has been submitted as an update to Fedora 45.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-c221dbc190

Comment 2 Fedora Update System 2026-10-08 10:18:43 UTC

FEDORA-2026-dbd9eb6961 (python-django6-6.1.2-1.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-dbd9eb6961

Comment 3 Fedora Update System 2026-10-09 02:08:18 UTC

FEDORA-2026-c221dbc190 has been pushed to the Fedora 45 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-c221dbc190`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-c221dbc190

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2026-10-09 02:30:09 UTC

FEDORA-2026-dbd9eb6961 has been pushed to the Fedora 44 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-dbd9eb6961`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-dbd9eb6961

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2026-10-17 01:05:12 UTC

FEDORA-2026-dbd9eb6961 (python-django6-6.1.2-1.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.