Home

Description

An issue was discovered in 6.0 before 6.0.5 and 5.2 before 5.2.14. Response headers do not vary on cookies if a session is not modified, but `SESSION_SAVE_EVERY_REQUEST` is `True`. A remote attacker can steal a user's session after that user visits a cached public page. 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 Cantina for reporting this issue.

PUBLISHED Reserved 2026-04-01 | Published 2026-05-05 | Updated 2026-05-06 | Assigner DSF




LOW: 2.3CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Problem types

CWE-539: Use of Persistent Cookies Containing Sensitive Information

Product status

Default status
unaffected

6.0 (python) before 6.0.5
affected

6.0.5 (python)
unaffected

5.2 (python) before 5.2.14
affected

5.2.14 (python)
unaffected

Timeline

2026-03-11:Initial report received.
2026-04-01:Vulnerability confirmed.
2026-05-05:Security release issued.

Credits

Cantina reporter

Jake Howard remediation developer

Sarah Boyce coordinator

References

docs.djangoproject.com/en/dev/releases/security/ (Django security archive) vendor-advisory

groups.google.com/g/django-announce (Django releases announcements) mailing-list

www.djangoproject.com/weblog/2026/may/05/security-releases/ (Django security releases issued: 6.0.5 and 5.2.14) vendor-advisory

cve.org (CVE-2026-35192)

nvd.nist.gov (CVE-2026-35192)

Download JSON