How severe is CVE-2026-35193?

CVE-2026-35193 has a CVSS 3.x base score of 3.1, rated low severity. It is exploitable over network with high attack complexity, requires no privileges and user interaction. Impact on confidentiality is low, integrity none, and availability none.

Is CVE-2026-35193 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (28th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-35193?

CVE-2026-35193 affects Djangoproject Django. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-35193?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2026-35193 have an EU (EUVD) identifier?

Yes. CVE-2026-35193 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-34089.

When was CVE-2026-35193 published?

CVE-2026-35193 was published on 2026-06-03 and last updated on 2026-06-17.

CVE-2026-35193

CVE-2026-35193 is a low-severity vulnerability in Djangoproject Django with a CVSS 3.x base score of 3.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-524.

Key facts

Severity: Low (CVSS 3.x base score 3.1)
CVSS v4: 2.3
EPSS exploit prediction: 0% (28th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-34089
Weakness: CWE-524
Affected product: Djangoproject Django
Published: 2026-06-03
Last modified: 2026-06-17

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.

Frequently asked questions

What is 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.
How severe is CVE-2026-35193?: CVE-2026-35193 has a CVSS 3.x base score of 3.1, rated low severity. It is exploitable over network with high attack complexity, requires no privileges and user interaction. Impact on confidentiality is low, integrity none, and availability none.
Is CVE-2026-35193 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (28th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-35193?: CVE-2026-35193 affects Djangoproject Django. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-35193?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-35193 have an EU (EUVD) identifier?: Yes. CVE-2026-35193 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-34089.
When was CVE-2026-35193 published?: CVE-2026-35193 was published on 2026-06-03 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:djangoproject:django:*:*:*:*:*:*:*:*

More vulnerabilities in Djangoproject Django

CVE-2014-0474 — Critical (CVSS 10.0): The (1) FilePathField, (2) GenericIPAddressField, and (3) IPAddressField model field classes in Django before 1.4.11,…
CVE-2026-4277 — Critical (CVSS 9.8): An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. Add permissions on inline model…
CVE-2024-53908 — Critical (CVSS 9.8): An issue was discovered in Django 5.1 before 5.1.4, 5.0 before 5.0.10, and 4.2 before 4.2.17. Direct usage of the…
CVE-2023-31047 — Critical (CVSS 9.8): In Django 3.2 before 3.2.19, 4.x before 4.1.9, and 4.2 before 4.2.1, it was possible to bypass validation when using…
CVE-2022-34265 — Critical (CVSS 9.8): An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6. The Trunc() and Extract() database functions…
CVE-2022-28347 — Critical (CVSS 9.8): A SQL injection issue was discovered in QuerySet.explain() in Django 2.2 before 2.2.28, 3.2 before 3.2.13, and 4.0…

All CVEs affecting Djangoproject Django →

Other CWE-524 vulnerabilities

CVE-2026-53943 — Critical (CVSS 9.6): Ghost is a Node.js content management system. From until 6.37.0, when Ghost is behind a shared caching layer that…
CVE-2025-64762 — Critical (CVSS 9.1): The AuthKit library for Next.js provides convenient helpers for authentication and session management using WorkOS &…
CVE-2026-50170 — High (CVSS 7.5): Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and…
CVE-2026-48901 — High (CVSS 7.5): The InputFilter::getInstance() method omitted a security sensitive parameter from the instance cache key.
CVE-2024-27917 — High (CVSS 7.5): Shopware is an open commerce platform based on Symfony Framework and Vue. The Symfony Session Handler pops the Session…
CVE-2021-24027 — High (CVSS 7.5): A cache configuration issue prior to WhatsApp for Android v2.21.4.18 and WhatsApp Business for Android v2.21.4.18 may…

Browse all CWE-524 vulnerabilities →