CVE-2026-35193

published 3 Jun 2026 · updated 3 Jun 2026

Potential exposure of private data via missing Vary: Authorization in UpdateCacheMiddleware

3.1LowCVSS 3.1EPSS 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.15 and 6.0.6.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
djangoproject>=5.2 <5.2.15, >=6.0 <6.0.65.2.15, 6.0.6

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

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