CVE-2026-6873: Django: signed cookies are vulnerable to salt namespace collisions
Low CVSS 3.1
- OSV id
- GHSA-h7pc-vwp9-298g
- Also known as
- BIT-django-2026-6873, CVE-2026-6873, PYSEC-2026-199
- Published
- Last modified
Affected packages
Versions we track that it affects: django 5.0.6, django 4.2.11; django 5.0.6, django 4.2.11
How to fix it
django (PyPI)
Upgrade django to 5.2.15 or later.
# in requirements.txt: change the line to django==5.2.15
pip install -r requirements.txt
- If it is an indirect dependency, upgrade the package that depends on it, or add a minimum version constraint for it (e.g. in constraints.txt, or as a dependency in pyproject.toml).
- Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.
django (PyPI)
Upgrade django to 6.0.6 or later.
# in requirements.txt: change the line to django==6.0.6
pip install -r requirements.txt
- If it is an indirect dependency, upgrade the package that depends on it, or add a minimum version constraint for it (e.g. in constraints.txt, or as a dependency in pyproject.toml).
- Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.
Not sure whether your project uses an affected version? Check your lockfile below for free.
Details
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
- GHSA-h7pc-vwp9-298g on OSV.dev
- Advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-6873
- Web: https://github.com/django/django/commit/594360cbf58be7f56eb6da96d58644297c99ef85
- Web: https://github.com/django/django/commit/70d36515b9cc71700105a14b275583070d48b689
- Web: https://github.com/django/django/commit/c807d9c398022d23cb27518fa6ecaf343efb30cf
- Web: https://docs.djangoproject.com/en/dev/releases/security
- Package: https://github.com/django/django
- Web: https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2026-199.yaml
- Web: https://groups.google.com/g/django-announce
- Web: https://www.djangoproject.com/weblog/2026/jun/03/security-releases
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: GitHub Advisory Database via OSV.dev (CC-BY 4.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.