CVEvulnerability

CVE-2026-6873

2.3 LOW Published 2026-06-03 Modified 2026-07-21 Official page ↗
Status
Analyzed
Published
2026-06-03
Last modified
2026-07-21
Assigner
6a34fbeb-21d4-45e7-8e0a-62b95bc12c92
CVSS 4.0 (6a34fbeb-21d4-45e7-8e0a-62b95bc12c92)
2.3 LOW — CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
CVSS 3.1 (6a34fbeb-21d4-45e7-8e0a-62b95bc12c92)
3.1 LOW — CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
CVSS 3.1 ([email protected])
4.3 MEDIUM — CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Weaknesses
CWE-347

Description

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.

Affected configurations

• djangoproject django (>= 5.2 < 5.2.15) • djangoproject django (>= 6.0 < 6.0.6)

Related

Weakness · CWE (1)

  • CWE-347 Improper Verification of Cryptographic Signature weakness

References