CVE-2026-48588
Potential exposure of private data via cached Set-Cookie response
- State
- Published
- Severity
- 2.3 Low
- Published
- Jul 7, 2026
- Updated
- Jul 7, 2026
- Reserved
- May 21, 2026
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.
Scores
| CVSS | Score | Vector | Source |
|---|---|---|---|
| 4.0 | 2.3 Low | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N | DSF |
| 3.1 | 4.2 Medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N | DSF |
Weaknesses
- CWE-524 Use of Cache Containing Sensitive Information
Affected Products
| Product | Versions |
|---|---|
Djangodjangoproject |
|
References
- Django security archivevendor-advisory
- Django releases announcementsmailing-list
- Django security releases issued: 6.0.7 and 5.2.16vendor-advisory
Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.