Django up to 5.2.14/6.0.5 django.middleware.cache.UpdateCacheMiddleware case sensitivity

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Django up to 5.2.14/6.0.5. Impacted is an unknown function of the component django.middleware.cache.UpdateCacheMiddleware. This manipulation causes case sensitivity. This vulnerability is handled as CVE-2026-8404. The attack can be initiated remotely. There is not any exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability has been found in Django up to 5.2.14/6.0.5 and classified as problematic. Affected by this vulnerability is an unknown functionality of the component django.middleware.cache.UpdateCacheMiddleware. The manipulation with an unknown input leads to a case sensitivity vulnerability. The CWE definition for the vulnerability is CWE-178. The product does not properly account for differences in case sensitivity when accessing or determining the properties of a resource, leading to inconsistent results. 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 match `Cache-Control` response directives case-insensitively, which allows remote attackers to read responses that were incorrectly cached because their `Cache-Control` directives used uppercase or mixed-case values. 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 Ahmed Badawe for reporting this issue.

The weakness was released by Ahmed Badawe. It is possible to read the advisory at docs.djangoproject.com. This vulnerability is known as CVE-2026-8404 since 05/12/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/08/2026).

Upgrading to version 5.2.15 or 6.0.6 eliminates this vulnerability. The upgrade is hosted for download at docs.djangoproject.com.

The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-1807). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Affected

• Open Source Django

Productinfo

Type

• Content Management System

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

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion