Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-48587: 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(

18
Routine
LOW 3.1UPGRADE

CVE-2026-48587 is a low-severity flaw (CVSS 3.1) affecting django. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 a

Why this priority

  • No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score3.1 (Low)
Attack vectorNetwork (remote)
Attack complexityHigh
Privileges neededNone
User interactionRequired
EPSS exploit chance0.4% (top 70%)
CISA exploited listNo
WeaknessCWE-1023
Published2026-06-03
Last modified2026-07-21
Publisher (CNA): Django Software Foundation · Vendor: djangoproject

Share: LinkedIn · X · Reddit

Last updated 2026-07-21 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

djangoproject django UPGRADE
Affected: >= 5.2 and < 5.2.15 · >= 6.0 and < 6.0.6
Fixed in: 5.2.15, 6.0.6
Safe to downgrade to: a release before 5.2
1. Check installed version
apt-cache policy django || rpm -q django || django --version
2. UPGRADE to 5.2.15 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade django
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade django
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 5.2 (Debian / Ubuntu)
apt-cache madison django sudo apt install django=<VERSION_BEFORE_5.2> sudo apt-mark hold django
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list django sudo dnf downgrade django-<VERSION_BEFORE_5.2> sudo dnf versionlock add django
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-48587?

django: upgrade to 5.2.15, 6.0.6. Exact commands for each OS are on this page.

Is CVE-2026-48587 being exploited?

CVE-2026-48587 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-48587 affect?

CVE-2026-48587 affects django. Severity is low (CVSS 3.1). 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 remo

How urgent is CVE-2026-48587?

Priority 18/100. No elevated risk signals yet.

Software pages

Django vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.