Back to feed
EUVD-2026-9294 · Published Mar 3, 2026
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.
Technologies
Djangoproject DjangoDjango Django
Weaknesses
CWE-770CWE-400
CVSS scores
- v3.17.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
MITRE ATT&CK
InferredWhere this vulnerability fits in an attack
Initial Access Impact
References
- https://docs.djangoproject.com/en/dev/releases/security/
- https://groups.google.com/g/django-announce
- https://www.djangoproject.com/weblog/2026/mar/03/security-releases/
- https://nvd.nist.gov/vuln/detail/CVE-2026-25673
- https://docs.djangoproject.com/en/dev/releases/security
- https://github.com/django/django
Potentially impacted assets
See if this affects your attack surface
