Is CVE-2026-48588 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-48588 being exploited in the wild.

How severe is CVE-2026-48588?

Low severity, with a CVSS score of 3.1, published 7 July 2026.

Which products and versions are affected?

Django (PyPI) ECOSYSTEM:introduced=0,fixed=5.2.16, ECOSYSTEM:introduced=5.2,fixed=5.2.16,introduced=6.0,fixed=6.0.7.

Is there a fix for CVE-2026-48588?

Yes. Django (PyPI): upgrade to 5.2.16, 6.0.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-48588 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-48588?

Check whether you run Django (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-48588: Django private data exposure in UpdateCacheMiddleware caching

CVE-2026-48588 · Severity: low · CVSS 3.1 · Published 2026-07-07

A vulnerability in Django's caching system could allow sensitive information to be accidentally shared between different users. When the system processes requests containing certain cookies, it may incorrectly store private responses in a shared cache, making them accessible to other visitors. This could lead to the exposure of private data or session information to unauthorized parties.

Technologies: Django (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-48588 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-48588 being exploited in the wild.
How severe is CVE-2026-48588?: Low severity, with a CVSS score of 3.1, published 7 July 2026.
Which products and versions are affected?: Django (PyPI) ECOSYSTEM:introduced=0,fixed=5.2.16, ECOSYSTEM:introduced=5.2,fixed=5.2.16,introduced=6.0,fixed=6.0.7.
Is there a fix for CVE-2026-48588?: Yes. Django (PyPI): upgrade to 5.2.16, 6.0.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-48588 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-48588?: Check whether you run Django (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Django (PyPI): upgrade to 5.2.16, 6.0.7 or later
```
pip install "Django>=6.0.7"
```

Technical details

A vulnerability exists in Django's UpdateCacheMiddleware and the cache_page() decorator where responses that vary on cookies are incorrectly cached when an incoming request contains unrelated cookies. This flaw in the cache key generation logic allows a remote attacker to potentially retrieve private data from a shared cache that was intended for a different user. The issue affects Django versions 5.2.x before 5.2.16 and 6.0.x before 6.0.7; older unsupported versions like 5.0.x and 4.2.x may also be vulnerable. Users are advised to upgrade to the patched versions (5.2.16 or 6.0.7) to ensure proper cache isolation.

Affected products

Django Software Foundation Django 5.2 before 5.2.16, 6.0 before 6.0.7

Identifiers

CVE-2026-48588
GHSA-3h9f-r86x-qvjx
PYSEC-2026-2090

Timeline

2026-07-07: disclosed
2026-07-07: advisory
2026-07-07: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.