djangoproject Django up to 5.2.14/6.0.5 django.middleware.cache.UpdateCacheMiddleware cache containing sensitive information

Summaryinfo

A vulnerability has been found in djangoproject Django up to 5.2.14/6.0.5 and classified as problematic. This issue affects some unknown processing of the component django.middleware.cache.UpdateCacheMiddleware. This manipulation causes use of cache containing sensitive information. The identification of this vulnerability is CVE-2026-35193. It is possible to initiate the attack remotely. There is no exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability classified as problematic was found in djangoproject Django up to 5.2.14/6.0.5. Affected by this vulnerability is an unknown part of the component django.middleware.cache.UpdateCacheMiddleware. The manipulation with an unknown input leads to a use of cache containing sensitive information vulnerability. The CWE definition for the vulnerability is CWE-524. The code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere. As an impact it is known to affect confidentiality. The summary by CVE is:

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.

The weakness was shared by Shai Berger. It is possible to read the advisory at docs.djangoproject.com. This vulnerability is known as CVE-2026-35193 since 04/01/2026. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/03/2026). The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.

Upgrading to version 5.2.15 or 6.0.6 eliminates this vulnerability.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

• Content Management System

Vendor

• djangoproject

Name

• Django

Version

• 5.2.0
• 5.2.1
• 5.2.2
• 5.2.3
• 5.2.4
• 5.2.5
• 5.2.6
• 5.2.7
• 5.2.8
• 5.2.9
• 5.2.10
• 5.2.11
• 5.2.12
• 5.2.13
• 5.2.14
• 6.0.0
• 6.0.1
• 6.0.2
• 6.0.3
• 6.0.4
• 6.0.5

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion