django
Affected
- introduced
5.2, fixed5.2.15, introduced6.0, fixed6.0.6(ecosystem)
Fixed versions
5.2.15, 6.0.6
Fix
- Fixed version
5.2.15pip install --upgrade django==5.2.15 - Fixed version
6.0.6pip install --upgrade django==6.0.6
Advisory
Also known as: BIT-django-2026-6873, CVE-2026-6873, GHSA-h7pc-vwp9-298g
The record has no summary.
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.
Medium Basis: CVSS v3 score 4.3, vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
5.2, fixed 5.2.15, introduced 6.0, fixed 6.0.6 (ecosystem)5.2.15, 6.0.6
5.2.15pip install --upgrade django==5.2.156.0.6pip install --upgrade django==6.0.6Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: PyPA Advisory Database · CC BY 4.0