CVE-2026-6873: Signed cookie salt namespace collision in django.http.HttpRequest.get_signed_cookie
An issue was discovered in Django 6.0 before 6.0.6 and 5.2 before 5.2.15. django.http.HttpRequest.getsignedcookie 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 Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Djangoto a version that resolves this vulnerability.Fixed in 6.0.6 - Upgrade
Upgrade
Djangoto a version that resolves this vulnerability.Fixed in 5.2.15
Event History
Frequently Asked Questions
What is the severity of CVE-2026-6873?
The severity of CVE-2026-6873 is classified as low with a score of 2.3.
How do I fix CVE-2026-6873?
To fix CVE-2026-6873, upgrade to Django versions 6.0.6 or 5.2.15 or later.
What systems are affected by CVE-2026-6873?
CVE-2026-6873 affects Django versions prior to 6.0.6 and 5.2.15.
What is the impact of CVE-2026-6873?
CVE-2026-6873 allows a remote attacker to potentially use a signed cookie in an inappropriate context.
Is there a workaround for CVE-2026-6873?
There are no specific workarounds; upgrading Django is the recommended solution.