Vulnerability in Djangoproject Django

CVE-2026-35193

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.

Published · last modified .

CVSS v3 metric

CVSS v3 base score 3.1 (Low). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N.

EPSS exploit prediction

EPSS: 0.004 (36.1th percentile), scored .

Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 36th percentile — 36.1% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2026-35193: held from 0.004 to 0.004.

EPSS over last 30 days · oldest: 0.004 · newest: 0.004 · change: +0.001

Affected products

Weakness classification (CWE)

References

Frequently asked questions

What is CVE-2026-35193?
CVE-2026-35193 is a low-severity vulnerability in Djangoproject Django, classified under Use of Cache Containing Sensitive Information. CVSS score: 3.1/10. Published 2026-06-03.
How severe is CVE-2026-35193?
Low severity. CVSS v3 base score is 3.1 out of 10.