CVE-2025-64458: Potential denial-of-service vulnerability in HttpResponseRedirect and HttpResponsePermanentRedirect on Windows
An issue was discovered in 5.1 before 5.1.14, 4.2 before 4.2.26, and 5.2 before 5.2.8. NFKC normalization in Python is slow on Windows. As a consequence, django.http.HttpResponseRedirect, django.http.HttpResponsePermanentRedirect, and the shortcut django.shortcuts.redirect were subject to a potential denial-of-service attack via certain inputs with a very large number of Unicode 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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-64458?
CVE-2025-64458 is classified with a medium severity level due to its performance impact on NFKC normalization in Python on Windows.
How do I fix CVE-2025-64458?
To fix CVE-2025-64458, upgrade to Django versions 5.1.14, 4.2.26, or 5.2.8 or newer.
Which Django versions are affected by CVE-2025-64458?
CVE-2025-64458 affects Django versions prior to 5.1.14, 4.2.26, and 5.2.8.
Does CVE-2025-64458 affect Django on platforms other than Windows?
CVE-2025-64458 specifically impacts Django's performance on Windows; other platforms may not be affected in the same way.
What components of Django are impacted by CVE-2025-64458?
CVE-2025-64458 affects the `django.http.HttpResponseRedirect`, `django.http.HttpResponsePermanentRedirect`, and `django.shortcuts.redirect` components.