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

Published Jun 3, 2026
·
Updated

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 Software

3 affected components
Django Software Foundation Django>=5.2<5.2.15, >=6.0<6.0.6
djangoproject Django>=5.2<5.2.15
djangoproject Django>=6.0<6.0.6

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Django to a version that resolves this vulnerability.

    Fixed in 5.2.15
  2. Upgrade

    Upgrade Django to a version that resolves this vulnerability.

    Fixed in 6.0.6
  3. Configuration

    Update/patch Django so UpdateCacheMiddleware adds the Authorization value to the Vary response header when handling requests bearing an Authorization header but lacking Cache-Control: public, preventing private cached responses from being served to unauthenticated users.

    Django middleware.cache.UpdateCacheMiddleware Vary header = Include Authorization in Vary for requests with Authorization header (without Cache-Control: public)

Event History

Jun 3, 2026
CVE Published
via MITRE·01:16 PM
Data Sourced
via MITRE·01:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-35193?

The severity of CVE-2026-35193 is rated low with a score of 3.1.

2

How do I fix CVE-2026-35193?

To fix CVE-2026-35193, upgrade Django to version 5.2.15 or 6.0.6 or later.

3

What data is at risk due to CVE-2026-35193?

CVE-2026-35193 potentially exposes private data due to the missing Vary: Authorization in UpdateCacheMiddleware.

4

Which versions of Django are affected by CVE-2026-35193?

CVE-2026-35193 affects Django versions prior to 5.2.15 and 6.0.6.

5

What type of attack can exploit CVE-2026-35193?

CVE-2026-35193 can be exploited by remote attackers who can read private data due to improper caching behavior.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203