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.
EPSS: 0.004 (30.2th percentile) — read the EPSS interpretation.
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.
Affected products
- Djangoproject Django — versions 6.0, 6.0.6, 5.2
Weakness classification (CWE)
References
- 6a34fbeb-21d4-45e7-8e0a-62b95bc12c92 (vendor-advisory, Patch, Vendor Advisory)
- 6a34fbeb-21d4-45e7-8e0a-62b95bc12c92 (mailing-list, Release Notes)
- 6a34fbeb-21d4-45e7-8e0a-62b95bc12c92 (vendor-advisory, Patch, Vendor Advisory)
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.