CVE-2026-35192: CWE-539: Use of Persistent Cookies Containing Sensitive Information in djangoproject Django
A vulnerability in Django versions 6.0 before 6.0.5 and 5.2 before 5.2.14 allows a remote attacker to steal a user's session if the user visits a cached public page and the SESSION_SAVE_EVERY_REQUEST setting is enabled. The issue arises because response headers do not vary on cookies when the session is unmodified, potentially exposing persistent cookies containing sensitive information. Earlier unsupported Django versions may also be affected. The CVSS score is low (2.
AI Analysis
Technical Summary
CVE-2026-35192 is a vulnerability in Django web framework versions 6.0 (before 6.0.5) and 5.2 (before 5.2.14) where response headers fail to vary on cookies if the session is not modified but the SESSION_SAVE_EVERY_REQUEST setting is set to True. This behavior can allow a remote attacker to steal a user's session after the user visits a cached public page, due to the use of persistent cookies containing sensitive information. The issue is tracked under CWE-539 (Use of Persistent Cookies Containing Sensitive Information). Earlier unsupported Django versions such as 5.0.x, 4.1.x, and 3.2.x were not evaluated but may also be vulnerable. No official remediation level or patch links are provided in the data.
Potential Impact
The vulnerability could allow remote attackers to hijack user sessions by exploiting cached public pages when SESSION_SAVE_EVERY_REQUEST is enabled and the session is unmodified. This could lead to unauthorized access to user accounts or sensitive information stored in session cookies. However, the CVSS score of 2.3 indicates the overall impact is low, suggesting limited exploitability or impact scope.
Mitigation Recommendations
Patch status is not yet confirmed — check the official Django vendor advisory for current remediation guidance. Users should verify if they are running affected versions and consider upgrading to Django 6.0.5 or 5.2.14 or later once patches are officially released. As a temporary measure, disabling SESSION_SAVE_EVERY_REQUEST may reduce exposure. Monitor vendor communications for updates.
CVE-2026-35192: CWE-539: Use of Persistent Cookies Containing Sensitive Information in djangoproject Django
Description
A vulnerability in Django versions 6.0 before 6.0.5 and 5.2 before 5.2.14 allows a remote attacker to steal a user's session if the user visits a cached public page and the SESSION_SAVE_EVERY_REQUEST setting is enabled. The issue arises because response headers do not vary on cookies when the session is unmodified, potentially exposing persistent cookies containing sensitive information. Earlier unsupported Django versions may also be affected. The CVSS score is low (2.
CVSS v4.0
Score 2.3low
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-35192 is a vulnerability in Django web framework versions 6.0 (before 6.0.5) and 5.2 (before 5.2.14) where response headers fail to vary on cookies if the session is not modified but the SESSION_SAVE_EVERY_REQUEST setting is set to True. This behavior can allow a remote attacker to steal a user's session after the user visits a cached public page, due to the use of persistent cookies containing sensitive information. The issue is tracked under CWE-539 (Use of Persistent Cookies Containing Sensitive Information). Earlier unsupported Django versions such as 5.0.x, 4.1.x, and 3.2.x were not evaluated but may also be vulnerable. No official remediation level or patch links are provided in the data.
Potential Impact
The vulnerability could allow remote attackers to hijack user sessions by exploiting cached public pages when SESSION_SAVE_EVERY_REQUEST is enabled and the session is unmodified. This could lead to unauthorized access to user accounts or sensitive information stored in session cookies. However, the CVSS score of 2.3 indicates the overall impact is low, suggesting limited exploitability or impact scope.
Mitigation Recommendations
Patch status is not yet confirmed — check the official Django vendor advisory for current remediation guidance. Users should verify if they are running affected versions and consider upgrading to Django 6.0.5 or 5.2.14 or later once patches are officially released. As a temporary measure, disabling SESSION_SAVE_EVERY_REQUEST may reduce exposure. Monitor vendor 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/13/2026, 3:47:14 AM
Last updated: 6/20/2026, 8:43:52 AM
Views: 86
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.