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.
CVE-2026-15920
Score 6.1 from GitHub Security Advisory published 2026-08-04. a secondary CVSS source baseline 6.1; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.1
- EG Score
- 6.1(high)
- EG Risk
- 28(Track)EG Risk 28/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity61% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 23%
- KEV
- Not listed
Published
August 4, 2026
Last Modified
August 17, 2026
Advisory Details (7)
Auto-updated Aug 4, 2026Django security releases issued: 6.0.8 and 5.2.17 | Weblog | Django
https://www.djangoproject.com/weblog/2026/aug/04/security-releases/commit b9adb81339cc (django/django)
Fix landed in django/django commit b9adb81339cc — awaiting tagged release
https://github.com/django/django/commit/b9adb81339cc418f8f56b1050cca6dfec3ab6349commit 13debb622a32 (django/django)
Fix landed in django/django commit 13debb622a32 — awaiting tagged release
https://github.com/django/django/commit/13debb622a32720bda1bccda7622fd14fbf3931bcommit 5a260d309a4c (django/django)
Fix landed in django/django commit 5a260d309a4c — awaiting tagged release
https://github.com/django/django/commit/5a260d309a4c8010c2ebda24eb758a5d95e2508acommit 47511a21026c (django/django)
Fix landed in django/django commit 47511a21026c — awaiting tagged release
https://github.com/django/django/commit/47511a21026cdd721d8fbf8571cc079bc38bb46dArchive of security issues | Django documentation | Django
https://docs.djangoproject.com/en/dev/releases/security/Vendor Advisories for CVE-2026-15920(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| python-django | 2:2.2.24-1 ... 3:6.1~rc1-1 (185 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| python-django | 3:3.2.19-1 ... 3:6.1~rc1-1 (105 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| python-django | 3:4.2.23-1 ... 3:6.1~rc1-1 (61 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| python-django | 3:4.2.23-1 ... 3:6.1~rc1-1 (58 versions) | — | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 20× in last 7d / 50× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-20 23:00 UTCEG score recompute
- 2026-08-20 23:00 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 21:50 UTCEG score recompute
- 2026-08-19 21:50 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 20:39 UTCEG score recompute
- 2026-08-18 20:39 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 19:28 UTCEG score recompute
- 2026-08-17 19:28 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 01:49 UTCEG score recompute
- 2026-08-17 01:49 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-16 00:39 UTCEG score recompute
- 2026-08-16 00:39 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 23:28 UTCGHSA enrichment
- 2026-08-13 22:18 UTCEG score recompute
- 2026-08-13 22:18 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 21:08 UTCEG score recompute
- 2026-08-12 21:08 UTCGHSA enrichment
Show 25 moreShow fewer
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-12 02:36 UTCEG score recompute
- 2026-08-12 02:36 UTCGHSA enrichment
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-11 01:26 UTCEG score recompute
- 2026-08-11 01:26 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 00:16 UTCEG score recompute
- 2026-08-10 00:16 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-08 23:06 UTCEG score recompute
- 2026-08-08 23:06 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-07 21:55 UTCEG score recompute
- 2026-08-07 21:55 UTCGHSA enrichment
- 2026-08-06 20:45 UTCEG score recompute
- 2026-08-06 20:45 UTCGHSA enrichment
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-05 19:35 UTCEG score recompute
- 2026-08-05 19:35 UTCGHSA enrichment
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 18:25 UTCEG score recompute
- 2026-08-04 17:23 UTCEG score recompute
- 2026-08-04 16:28 UTCEG score recompute
- 2026-08-04 16:26 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-15920?
When was CVE-2026-15920 disclosed?
Is CVE-2026-15920 actively exploited?
What is the CVSS score of CVE-2026-15920?
How do I remediate CVE-2026-15920?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-15920
Is Your Infrastructure Affected by CVE-2026-15920?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.