CVE-2026-6873: Django: signed cookies are vulnerable to salt namespace collisions
(updated )
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.
References
- docs.djangoproject.com/en/dev/releases/security
- github.com/advisories/GHSA-h7pc-vwp9-298g
- github.com/django/django/commit/594360cbf58be7f56eb6da96d58644297c99ef85
- github.com/django/django/commit/70d36515b9cc71700105a14b275583070d48b689
- github.com/django/django/commit/c807d9c398022d23cb27518fa6ecaf343efb30cf
- github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2026-199.yaml
- groups.google.com/g/django-announce
- nvd.nist.gov/vuln/detail/CVE-2026-6873
- www.djangoproject.com/weblog/2026/jun/03/security-releases
Code Behaviors & Features
Detect and mitigate CVE-2026-6873 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →