Django up to 4.2.25/5.1.13/5.2.7 on Windows algorithmic complexity

Summaryinfo

A vulnerability was found in Django up to 4.2.25/5.1.13/5.2.7 on Windows. It has been classified as problematic. This affects the function Django.http.HttpResponseRedirect/Django.http.HttpResponsePermanentRedirect. This manipulation causes algorithmic complexity. This vulnerability appears as CVE-2025-64458. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability classified as problematic was found in Django up to 4.2.25/5.1.13/5.2.7 on Windows. Affected by this vulnerability is the function Django.http.HttpResponseRedirect/Django.http.HttpResponsePermanentRedirect. The manipulation with an unknown input leads to a algorithmic complexity vulnerability. The CWE definition for the vulnerability is CWE-407. An algorithm in a product has an inefficient worst-case computational complexity that may be detrimental to system performance and can be triggered by an attacker, typically using crafted manipulations that ensure that the worst case is being reached. As an impact it is known to affect availability. The summary by CVE is:

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.

The advisory is shared at docs.djangoproject.com. This vulnerability is known as CVE-2025-64458 since 11/04/2025. The exploitation appears to be easy. The attack can be launched remotely. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1499 for this issue.

The vulnerability scanner Nessus provides a plugin with the ID 274082 (Linux Distros Unpatched Vulnerability : CVE-2025-64458), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 4.2.26, 5.1.14 or 5.2.8 eliminates this vulnerability. The upgrade is hosted for download at docs.djangoproject.com.

The vulnerability is also documented in the databases at Tenable (274082), EUVD (EUVD-2025-37765) and CERT Bund (WID-SEC-2025-2495). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Affected

• Debian Linux
• Red Hat Enterprise Linux
• Fedora Linux
• SUSE Linux
• SUSE openSUSE
• Open Source Django

Productinfo

Type

• Content Management System

Name

• Django

Version

• 4.2.0
• 4.2.1
• 4.2.2
• 4.2.3
• 4.2.4
• 4.2.5
• 4.2.6
• 4.2.7
• 4.2.8
• 4.2.9
• 4.2.10
• 4.2.11
• 4.2.12
• 4.2.13
• 4.2.14
• 4.2.15
• 4.2.16
• 4.2.17
• 4.2.18
• 4.2.19
• 4.2.20
• 4.2.21
• 4.2.22
• 4.2.23
• 4.2.24
• 4.2.25
• 5.1.0
• 5.1.1
• 5.1.2
• 5.1.3
• 5.1.4
• 5.1.5
• 5.1.6
• 5.1.7
• 5.1.8
• 5.1.9
• 5.1.10
• 5.1.11
• 5.1.12
• 5.1.13
• 5.2.0
• 5.2.1
• 5.2.2
• 5.2.3
• 5.2.4
• 5.2.5
• 5.2.6
• 5.2.7

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion