CVE-2026-6873
LOW
2,3
Source: 6a34fbeb-21d4-45e7-8e0a-62b95bc12c92
Attack Vector: network
Attack Complexity: low
Privileges Required: low
User Interaction: none
Confidentiality: N/A
Integrity: N/A
Availability: N/A
LOW
3,1
Source: 6a34fbeb-21d4-45e7-8e0a-62b95bc12c92
Attack Vector: network
Attack Complexity: high
Privileges Required: low
User Interaction: none
Scope: unchanged
Confidentiality: low
Integrity: none
Availability: none
Description
AI Translation Available
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.
347
Improper Verification of Cryptographic Signature
DraftCommon Consequences
Security Scopes Affected:
Access Control
Integrity
Confidentiality
Potential Impacts:
Gain Privileges Or Assume Identity
Modify Application Data
Execute Unauthorized Code Or Commands
Applicable Platforms
All platforms may be affected
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/