CVE-2026-35193: CWE-524: Use of Cache Containing Sensitive Information in djangoproject Django
An issue was discovered in Django 5.2 before 5.2.15 and 6.0 before 6.0.6. `django.middleware.cache.UpdateCacheMiddleware` in Django does not add `Authorization` to the `Vary` response header for requests bearing that header without `Cache-Control: public`, which allows remote attackers to read private cached responses via unauthenticated requests to the same URL. 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 Shai Berger for reporting this issue.
AI Analysis
Technical Summary
CVE-2026-35193 is a vulnerability in Django's UpdateCacheMiddleware where the Authorization header is not added to the Vary response header for requests bearing that header unless Cache-Control: public is present. This can cause private cached responses to be served to unauthorized users making unauthenticated requests to the same URL. The flaw affects Django 5.2 versions before 5.2.15 and 6.0 versions before 6.0.6, with earlier unsupported versions potentially impacted. The CVSS score is 3.1, indicating low severity.
Potential Impact
The vulnerability allows remote attackers to read cached private responses that should be protected by authorization, potentially exposing sensitive information. However, the impact is limited to information disclosure with no integrity or availability impact. The low CVSS score reflects the limited scope and complexity of exploitation.
Mitigation Recommendations
A fix is available in Django versions 5.2.15 and 6.0.6 and later. Users should upgrade to these or newer versions to remediate the vulnerability. Since no official vendor advisory content was provided, patch status is inferred from the version ranges in the description. Check the official Django project advisories for confirmation and further guidance.
CVE-2026-35193: CWE-524: Use of Cache Containing Sensitive Information in djangoproject Django
Description
An issue was discovered in Django 5.2 before 5.2.15 and 6.0 before 6.0.6. `django.middleware.cache.UpdateCacheMiddleware` in Django does not add `Authorization` to the `Vary` response header for requests bearing that header without `Cache-Control: public`, which allows remote attackers to read private cached responses via unauthenticated requests to the same URL. 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 Shai Berger for reporting this issue.
CVSS v3.1
Score 3.1low
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-35193 is a vulnerability in Django's UpdateCacheMiddleware where the Authorization header is not added to the Vary response header for requests bearing that header unless Cache-Control: public is present. This can cause private cached responses to be served to unauthorized users making unauthenticated requests to the same URL. The flaw affects Django 5.2 versions before 5.2.15 and 6.0 versions before 6.0.6, with earlier unsupported versions potentially impacted. The CVSS score is 3.1, indicating low severity.
Potential Impact
The vulnerability allows remote attackers to read cached private responses that should be protected by authorization, potentially exposing sensitive information. However, the impact is limited to information disclosure with no integrity or availability impact. The low CVSS score reflects the limited scope and complexity of exploitation.
Mitigation Recommendations
A fix is available in Django versions 5.2.15 and 6.0.6 and later. Users should upgrade to these or newer versions to remediate the vulnerability. Since no official vendor advisory content was provided, patch status is inferred from the version ranges in the description. Check the official Django project advisories for confirmation and further guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- DSF
- Date Reserved
- 2026-04-01T18:21:23.779Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a2037c3e29bf47b50c14da5
Added to database: 6/3/2026, 2:18:43 PM
Last enriched: 6/3/2026, 2:49:07 PM
Last updated: 6/4/2026, 4:59:14 AM
Views: 3
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.