All reports
Low

django: Potential exposure of private data via empty and missing `Vary` headers

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-113593

Probability of exploitation in the next 30 days: 0.46%

FIRST EPSS · 2026-11-20

Description

An issue was discovered in Django 6.1 before 6.1.3, 6.0 before 6.0.10, and 5.2 before 5.2.19. The django.middleware.cache.UpdateCacheMiddleware and the django.views.decorators.cache.cache_page() decorator generate identical cache keys for requests that omit a header listed in the response’s Vary header and requests that include that header with an empty value, potentially allowing remote attackers to access private data cached for another request. Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected. Django would like to thank Andrew Gonzalez for reporting this issue.

A flaw was found in Django. This vulnerability leads to information disclosure due to improper cache key generation when handling HTTP headers. The caching mechanism treats web requests that omit a specified header identically to requests that supply the header with an empty value. As a result, a remote attacker could receive cached responses intended for other requests, potentially exposing private data.