CVE-2026-48588

published 7 Jul 2026 · updated 7 Jul 2026

Potential exposure of private data via cached Set-Cookie response

4.2MediumCVSS 4.2EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 5.2.16 and 6.0.7.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
djangoproject>=5.2 <5.2.16, >=6.0 <6.0.75.2.16, 6.0.7

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-48588 severity on Zeptric[![CVE-2026-48588](https://zeptric.io/badge/cve/CVE-2026-48588.svg)](https://zeptric.io/cve/CVE-2026-48588)