CVE-2026-48588: CWE-524: Use of Cache Containing Sensitive Information in djangoproject Django
An issue was discovered in Django 6.0 before 6.0.7 and 5.2 before 5.2.16. `UpdateCacheMiddleware` and the `cache_page()` decorator cache responses that vary on cookies when the incoming request carries unrelated cookies, which allows remote attackers to read private data from the shared cache. 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 Chris Whyland for reporting this issue.
AI Analysis
Technical Summary
CVE-2026-48588 is a medium severity vulnerability in Django's caching system affecting versions 6.0 prior to 6.0.7 and 5.2 prior to 5.2.16. The issue arises because UpdateCacheMiddleware and the cache_page() decorator cache responses that vary on cookies, but when the incoming request carries unrelated cookies, the cache may serve private data to unauthorized users. This is classified under CWE-524 (Use of Cache Containing Sensitive Information). The vulnerability was reported by Chris Whyland. Earlier unsupported Django versions such as 5.0.x, 4.1.x, and 3.2.x were not evaluated and may also be vulnerable but no confirmation is provided.
Potential Impact
An attacker can remotely read private data from the shared cache due to improper handling of cached responses that vary on cookies. This can lead to unauthorized disclosure of sensitive information. The CVSS score is 4.2 (medium), indicating limited impact with low complexity and no privileges required but user interaction needed.
Mitigation Recommendations
A patch is available for this vulnerability. Users should upgrade Django to version 6.0.7 or later if using the 6.0 series, or 5.2.16 or later if using the 5.2 series. For earlier unsupported versions, users should consider upgrading to a supported version that includes the fix. No additional mitigation steps are specified by the vendor advisory.
CVE-2026-48588: CWE-524: Use of Cache Containing Sensitive Information in djangoproject Django
Description
An issue was discovered in Django 6.0 before 6.0.7 and 5.2 before 5.2.16. `UpdateCacheMiddleware` and the `cache_page()` decorator cache responses that vary on cookies when the incoming request carries unrelated cookies, which allows remote attackers to read private data from the shared cache. 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 Chris Whyland for reporting this issue.
CVSS v3.1
Score 4.2medium
Affected software
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-48588 is a medium severity vulnerability in Django's caching system affecting versions 6.0 prior to 6.0.7 and 5.2 prior to 5.2.16. The issue arises because UpdateCacheMiddleware and the cache_page() decorator cache responses that vary on cookies, but when the incoming request carries unrelated cookies, the cache may serve private data to unauthorized users. This is classified under CWE-524 (Use of Cache Containing Sensitive Information). The vulnerability was reported by Chris Whyland. Earlier unsupported Django versions such as 5.0.x, 4.1.x, and 3.2.x were not evaluated and may also be vulnerable but no confirmation is provided.
Potential Impact
An attacker can remotely read private data from the shared cache due to improper handling of cached responses that vary on cookies. This can lead to unauthorized disclosure of sensitive information. The CVSS score is 4.2 (medium), indicating limited impact with low complexity and no privileges required but user interaction needed.
Mitigation Recommendations
A patch is available for this vulnerability. Users should upgrade Django to version 6.0.7 or later if using the 6.0 series, or 5.2.16 or later if using the 5.2 series. For earlier unsupported versions, users should consider upgrading to a supported version that includes the fix. No additional mitigation steps are specified by the vendor advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- DSF
- Date Reserved
- 2026-05-21T20:50:32.466Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a4d1440c9d9e3dbe35d5c79
Added to database: 07/07/2026, 14:59:12 UTC
Last enriched: 08/08/2026, 15:14:02 UTC
Last updated: 08/19/2026, 22:52:13 UTC
Views: 99
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.