All reports
Low

Django: has_vary_header may expose cached responses when Vary values contain whitespace

Affected versions

Version ranges need review.

Affected versions
>= 6.0.0, < 6.0.6
Fixed version
6.0.6
Affected versions
>=5.2 <5.2.15 || >=6.0 <6.0.6
Fixed version
5.2.15 · 6.0.6
Affected versions
< 5.2.15
Fixed version
5.2.15
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-48587

Probability of exploitation in the next 30 days: 0.37%

FIRST EPSS · 2026-11-20

Description

An issue was discovered in Django 5.2 before 5.2.15 and 6.0 before 6.0.6. django.utils.cache.has_vary_header() in Django does not strip leading or trailing whitespace from Vary response header values before comparison, which allows remote attackers to read cached responses via requests to URLs whose responses contain whitespace-padded Vary header 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 Navid Rezazadeh for reporting this issue.

Links

Credits

  • cgurnik