Django up to 5.2.14/6.0.5 django.http.HttpRequest.get_signed_cookie salt signature verification

Summaryinfo

A vulnerability classified as problematic has been found in Django up to 5.2.14/6.0.5. This vulnerability affects the function django.http.HttpRequest.get_signed_cookie. The manipulation of the argument salt leads to signature verification. This vulnerability is traded as CVE-2026-6873. It is possible to initiate the attack remotely. There is no exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in Django up to 5.2.14/6.0.5. This issue affects the function django.http.HttpRequest.get_signed_cookie. The manipulation of the argument salt with an unknown input leads to a signature verification vulnerability. Using CWE to declare the problem leads to CWE-347. The product does not verify, or incorrectly verifies, the cryptographic signature for data. Impacted is confidentiality. The summary by CVE is:

An issue was discovered in Django 6.0 before 6.0.6 and 5.2 before 5.2.15. `django.http.HttpRequest.get_signed_cookie` in Django uses a non-injective salt derivation (concatenating the cookie name and salt argument), which allows a remote attacker to use a cookie in a context different from the one where it was signed, via distinct `(name, salt)` pairs that produce the same concatenation. 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 Peng Zhou for reporting this issue.

The weakness was shared by Peng Zhou. The advisory is shared at docs.djangoproject.com. The identification of this vulnerability is CVE-2026-6873 since 04/22/2026. The exploitation is known to be difficult. The attack may be initiated remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/04/2026).

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

Upgrading to version 5.2.15 or 6.0.6 eliminates this vulnerability. The upgrade is hosted for download at docs.djangoproject.com.

The vulnerability is also documented in the vulnerability database at Tenable (318412). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Content Management System

Name

• Django

Version

• 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
• 5.2.11
• 5.2.12
• 5.2.13
• 5.2.14
• 6.0.0
• 6.0.1
• 6.0.2
• 6.0.3
• 6.0.4
• 6.0.5

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