What’s Vulnerable › Vulnerabilities

CVE-2026-6873: Signed cookie salt namespace collision in django.http.HttpRequest.get_signed_cookie

• Severity: medium (CVSS 4.3 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.2% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2026-06-03 · updated 2026-07-21
• Weakness: CWE-347

Description

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.

Affected products

• Django: from 5.2 before 5.2.15; from 6.0 before 6.0.6 — fixed in 5.2.15, 6.0.6
• Pypi Django: before 5.2.15; from 6.0.0 before 6.0.6; 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.1, 1.1.1 (+422) — fixed in 5.2.15, 6.0.6

How to fix

Upgrade to a fixed version: Django 5.2.15, 6.0.6; Pypi Django 5.2.15, 6.0.6. Check the vendor advisory for mitigations.

References

• https://docs.djangoproject.com/en/dev/releases/security/
• https://groups.google.com/g/django-announce
• https://www.djangoproject.com/weblog/2026/jun/03/security-releases/

Get alerted when CVE-2026-6873 or the next vulnerability affects your stack