CVEvulnerability

CVE-2026-35193

2.3 LOW Published 2026-06-03 Modified 2026-07-21 Official page ↗
Status
Analyzed
Published
2026-06-03
Last modified
2026-07-21
Assigner
6a34fbeb-21d4-45e7-8e0a-62b95bc12c92
CVSS 4.0 (6a34fbeb-21d4-45e7-8e0a-62b95bc12c92)
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
CVSS 3.1 (6a34fbeb-21d4-45e7-8e0a-62b95bc12c92)
3.1 LOW — CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
Weaknesses
CWE-524

Description

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 configurations

• djangoproject django (>= 5.2 < 5.2.15) • djangoproject django (>= 6.0 < 6.0.6)

Related

Weakness · CWE (1)

  • CWE-524 Use of Cache Containing Sensitive Information weakness

References