CVE-2026-15920

Name	CVE-2026-15920
Description	An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. `django.contrib.admin.utils.display_for_field()` renders `URLField` values as clickable links in the admin without validating the URL. A value stored with an unsafe scheme is displayed as a link on changelist and read-only admin pages, which allows cross-site scripting against staff users who click the link. Exploitation requires the unsafe value to already be stored in the database. `URLField` validation through a `ModelForm` or the admin rejects unsafe schemes, so this affects applications that persist `URLField` data without running model validation, for example through direct queryset writes, deserialization, or bulk import of untrusted input. Django would like to thank Egor Saltykov for reporting this issue.
Source	CVE (at NVD; CERT, ENISA, LWN, oss-sec, fulldisc, Debian ELTS, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more)
Debian Bugs	1143611

Vulnerable and fixed packages

The table below lists information on source packages.

Source Package	Release	Version	Status
python-django (PTS)	bullseye	2:2.2.28-1~deb11u2	vulnerable
	bullseye (security)	2:2.2.28-1~deb11u12	vulnerable
	bookworm	3:3.2.25-0+deb12u3	vulnerable
	bookworm (security)	3:3.2.25-0+deb12u2	vulnerable
	trixie	3:4.2.28-0+deb13u2	vulnerable
	trixie (security)	3:4.2.28-0+deb13u1	vulnerable
	forky	3:5.2.16-1	vulnerable
	sid	3:5.2.17-1	fixed

The information below is based on the following data on fixed versions.

Package	Type	Release	Fixed Version	Urgency	Origin	Debian Bugs
python-django	source	(unstable)	3:5.2.17-1			1143611

Notes

https://www.djangoproject.com/weblog/2026/aug/04/security-releases/
Fixed by: https://github.com/django/django/commit/b9adb81339cc418f8f56b1050cca6dfec3ab6349 (5.2.17)