CVE-2026-35192: CWE-539: Use of Persistent Cookies Containing Sensitive Information in djangoproject Django
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.
AI Analysis
Technical Summary
This vulnerability involves the use of persistent cookies containing sensitive information due to improper handling of response headers when SESSION_SAVE_EVERY_REQUEST is set to True. Specifically, if a session is not modified, the response headers do not vary on cookies, which can lead to session theft via cached public pages. The issue affects Django versions 6.0 before 6.0.5 and 5.2 before 5.2.14, with potential impact on earlier unsupported versions. The CVSS 4.0 base score is 2.3, indicating low severity.
Potential Impact
An attacker can steal a user's session cookie after the user visits a cached public page, potentially leading to session hijacking. The impact is limited by the low CVSS score and the requirement that SESSION_SAVE_EVERY_REQUEST is enabled. There is no indication of privilege escalation or remote code execution.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, consider disabling SESSION_SAVE_EVERY_REQUEST or implementing alternative session management strategies to avoid exposure. Monitor official Django project communications for updates.
CVE-2026-35192: CWE-539: Use of Persistent Cookies Containing Sensitive Information in djangoproject Django
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability involves the use of persistent cookies containing sensitive information due to improper handling of response headers when SESSION_SAVE_EVERY_REQUEST is set to True. Specifically, if a session is not modified, the response headers do not vary on cookies, which can lead to session theft via cached public pages. The issue affects Django versions 6.0 before 6.0.5 and 5.2 before 5.2.14, with potential impact on earlier unsupported versions. The CVSS 4.0 base score is 2.3, indicating low severity.
Potential Impact
An attacker can steal a user's session cookie after the user visits a cached public page, potentially leading to session hijacking. The impact is limited by the low CVSS score and the requirement that SESSION_SAVE_EVERY_REQUEST is enabled. There is no indication of privilege escalation or remote code execution.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, consider disabling SESSION_SAVE_EVERY_REQUEST or implementing alternative session management strategies to avoid exposure. Monitor official Django project communications for updates.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- DSF
- Date Reserved
- 2026-04-01T18:21:23.779Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69fa191dcbff5d86100ff6d4
Added to database: 5/5/2026, 4:21:49 PM
Last enriched: 5/5/2026, 4:38:08 PM
Last updated: 5/6/2026, 3:55:05 AM
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.