CVE-2026-48588: An issue was discovered in Django 6.0 before 6.0.7 and 5.2 before 5.2.16. `UpdateCacheMiddleware` and the `cac

Routine

LOW 3.1UPGRADE

CVE-2026-48588 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 6.0 before 6.0.7 and 5.2 before 5.2.16. `UpdateCacheMiddleware` and the `cache_page()` decorator cache responses that vary on cookies when the incoming request carries unrelated cookies, which allows remote attackers to read private data from the shared cache. 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 Chris Whyland

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	3.1 (Low)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.4% (top 63%)
CISA exploited list	No
Weakness	CWE-524
Published	2026-07-07
Last modified	2026-10-25

Publisher (CNA): Django Software Foundation · Vendor: djangoproject

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

Am I affected?

Timeline

2026-07-07 15:16 UTCPublished CVE record published
2026-10-25 20:10 UTCUpdated Record last modified

djangoproject django UPGRADE

Affected: >= 5.2 and < 5.2.16 · >= 6.0 and < 6.0.7

Fixed in: 5.2.16, 6.0.7

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.16 (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-48588?

django: upgrade to 5.2.16, 6.0.7. Exact commands for each OS are on this page.

Is CVE-2026-48588 being exploited?

CVE-2026-48588 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-48588 affect?

CVE-2026-48588 affects django. Severity is low (CVSS 3.1). An issue was discovered in Django 6.0 before 6.0.7 and 5.2 before 5.2.16. `UpdateCacheMiddleware` and the `cache_page()` decorator cache responses that vary on cookies when the incoming request carries unrelated cookies, which allows remote

How urgent is CVE-2026-48588?

Priority 20/100. No elevated risk signals yet.

Software pages

Django vulnerabilities

Related CVEs

CVE-2026-53877 MEDIUM 4.8 UPGRADE An issue was discovered in Django 6.0 before 6.0.7 and 5.2 before 5.2.16. `django.contrib.gis.gdal.GDALRaster`
CVE-2026-53878 MEDIUM 6.1 UPGRADE An issue was discovered in Django 6.0 before 6.0.7 and 5.2 before 5.2.16. `DomainNameValidator` does not prohi
CVE-2026-15307 HIGH 8.8 UPGRADE An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. GeoDjango spatial lookups optimistic
CVE-2026-15830 MEDIUM 5.3 UPGRADE An issue was discovered in Django 6.0 before 6.0.9 and 5.2 before 5.2.18. GeoDjango's `django.contrib.gis.geos
CVE-2026-15337 MEDIUM 5.3 UPGRADE An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. `django.utils.translation.check_for_

References

← Back to latest CVEs