Django up to 4.2.27/5.2.10/6.0.1 ASGIRequest algorithmic complexity

Summaryinfo

A vulnerability was found in Django up to 4.2.27/5.2.10/6.0.1 and classified as problematic. This vulnerability affects unknown code of the component ASGIRequest. Executing a manipulation can lead to algorithmic complexity. The identification of this vulnerability is CVE-2025-14550. The attack may be launched remotely. There is no exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability has been found in Django up to 4.2.27/5.2.10/6.0.1 and classified as problematic. This vulnerability affects an unknown code of the component ASGIRequest. 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. CVE summarizes:

An issue was discovered in 6.0 before 6.0.2, 5.2 before 5.2.11, and 4.2 before 4.2.28. `ASGIRequest` allows a remote attacker to cause a potential denial-of-service via a crafted request with multiple duplicate headers. 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 Jiyong Yang for reporting this issue.

The advisory is shared for download at docs.djangoproject.com. This vulnerability was named CVE-2025-14550 since 12/11/2025. The exploitation appears to be easy. The attack can be initiated remotely. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1499.

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

Upgrading to version 4.2.28, 5.2.11 or 6.0.2 eliminates this vulnerability.

The vulnerability is also documented in the databases at Tenable (297743) and CERT Bund (WID-SEC-2026-0297). VulDB is the best source for vulnerability data and more expert information about this specific topic.

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
• 4.2.26
• 4.2.27
• 5.2.0
• 5.2.1
• 5.2.2
• 5.2.3
• 5.2.4
• 5.2.5
• 5.2.6
• 5.2.7
• 5.2.8
• 5.2.9
• 5.2.10
• 6.0.0
• 6.0.1

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion