CVE-2026-35193: CWE-524: Use of Cache Containing Sensitive Information in djangoproject Django
A vulnerability in Django's UpdateCacheMiddleware allows private cached responses to be read by unauthenticated remote attackers. This occurs because the middleware does not add the Authorization header to the Vary response header for requests that include Authorization without Cache-Control: public. The issue affects Django versions 5.2 before 5.2.15 and 6.0 before 6.0.6. Earlier unsupported versions may also be affected. The vulnerability has a low severity score and no known exploits in the wild.
AI Analysis
Technical Summary
CVE-2026-35193 is a vulnerability in Django's middleware cache handling where the UpdateCacheMiddleware fails to include the Authorization header in the Vary response header for requests bearing Authorization without Cache-Control: public. This omission allows remote attackers to retrieve private cached responses via unauthenticated requests to the same URL. The flaw affects Django versions 5.2 prior to 5.2.15 and 6.0 prior to 6.0.6. Unsupported earlier versions such as 5.0.x, 4.1.x, and 3.2.x were not evaluated but may also be vulnerable. The issue is tracked under CWE-524 (Use of Cache Containing Sensitive Information).
Potential Impact
The vulnerability enables remote attackers to access private cached responses without authentication by exploiting the lack of Authorization header inclusion in the Vary response header. This could lead to unauthorized disclosure of sensitive information cached by the application. The CVSS score is 3.1 (low severity), indicating limited impact and requiring user interaction with high attack complexity.
Mitigation Recommendations
A patch is available for this vulnerability. Users should upgrade Django to version 5.2.15 or later, or 6.0.6 or later to remediate the issue. There is no indication that earlier unsupported versions have official fixes; users of those versions should consider upgrading to a supported patched release. No additional mitigation steps are specified by the vendor.
CVE-2026-35193: CWE-524: Use of Cache Containing Sensitive Information in djangoproject Django
Description
A vulnerability in Django's UpdateCacheMiddleware allows private cached responses to be read by unauthenticated remote attackers. This occurs because the middleware does not add the Authorization header to the Vary response header for requests that include Authorization without Cache-Control: public. The issue affects Django versions 5.2 before 5.2.15 and 6.0 before 6.0.6. Earlier unsupported versions may also be affected. The vulnerability has a low severity score and no known exploits in the wild.
CVSS v3.1
Score 3.1low
Affected software
djangoproject
Django
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-35193 is a vulnerability in Django's middleware cache handling where the UpdateCacheMiddleware fails to include the Authorization header in the Vary response header for requests bearing Authorization without Cache-Control: public. This omission allows remote attackers to retrieve private cached responses via unauthenticated requests to the same URL. The flaw affects Django versions 5.2 prior to 5.2.15 and 6.0 prior to 6.0.6. Unsupported earlier versions such as 5.0.x, 4.1.x, and 3.2.x were not evaluated but may also be vulnerable. The issue is tracked under CWE-524 (Use of Cache Containing Sensitive Information).
Potential Impact
The vulnerability enables remote attackers to access private cached responses without authentication by exploiting the lack of Authorization header inclusion in the Vary response header. This could lead to unauthorized disclosure of sensitive information cached by the application. The CVSS score is 3.1 (low severity), indicating limited impact and requiring user interaction with high attack complexity.
Mitigation Recommendations
A patch is available for this vulnerability. Users should upgrade Django to version 5.2.15 or later, or 6.0.6 or later to remediate the issue. There is no indication that earlier unsupported versions have official fixes; users of those versions should consider upgrading to a supported patched release. No additional mitigation steps are specified by the vendor.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- DSF
- Date Reserved
- 2026-04-01T18:21:23.779Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a2037c3e29bf47b50c14da5
Added to database: 06/03/2026, 14:18:43 UTC
Last enriched: 08/08/2026, 15:14:44 UTC
Last updated: 09/14/2026, 10:01:30 UTC
Views: 88
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.