django
Affected
- introduced
6.0, fixed6.0.3(ecosystem)
Fixed versions
6.0.3
Fix
- Fixed version
6.0.3pip install --upgrade django==6.0.3
Advisory
Also known as: BIT-django-2026-25673, CVE-2026-25673, PYSEC-2026-2448
Django vulnerable to Uncontrolled Resource Consumption
An issue was discovered in 6.0 before 6.0.3, 5.2 before 5.2.12, and 4.2 before 4.2.29.
URLField.to_python() in Django calls urllib.parse.urlsplit(), which performs NFKC normalization on Windows that is disproportionately slow for certain Unicode characters, allowing a remote attacker to cause denial of service via large URL inputs containing these characters.
Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank Seokchan Yoon for reporting this issue.
High Basis: The source's own band: HIGH
6.0, fixed 6.0.3 (ecosystem)6.0.3
6.0.3pip install --upgrade django==6.0.35.2, fixed 5.2.12 (ecosystem)5.2.12
5.2.12pip install --upgrade django==5.2.124.2, fixed 4.2.29 (ecosystem)4.2.29
4.2.29pip install --upgrade django==4.2.29Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0