What’s Vulnerable › Vulnerabilities

CVE-2026-35193: Potential exposure of private data via missing Vary: Authorization in UpdateCacheMiddleware

• Severity: low (CVSS 3.1 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.4% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2026-06-03 · updated 2026-07-21
• Weakness: 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 products

• Django: from 5.2 before 5.2.15; from 6.0 before 6.0.6 — fixed in 5.2.15, 6.0.6

How to fix

Upgrade to a fixed version: Django 5.2.15, 6.0.6. Check the vendor advisory for mitigations.

References

• https://docs.djangoproject.com/en/dev/releases/security/
• https://groups.google.com/g/django-announce
• https://www.djangoproject.com/weblog/2026/jun/03/security-releases/

Get alerted when CVE-2026-35193 or the next vulnerability affects your stack