CVE-2026-48588

What it is

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 for reporting this issue.

At a glance

Exploitability

Can be exploited over the network without logging in, but needs a user to act. Limited direct impact.

Exploit odds

0.4% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-07-07 15:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-25 20:10 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.4% in the next 30 days (EPSS).
• Severity: 2.3 LOW (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-07-07 15:16 UTC

Last modified

2026-10-25 20:10 UTC

Exploit probability

0.4% · EPSS, next 30 days

Weakness

CWE-524

Record status

Analyzed

Affected

• Djangoproject Django < 5.2.16
• Djangoproject Django < 6.0.7

Attack profile CVSS 4.0 · 2.3

Attack vector

Network

Complexity

Low

Attack requirements

Present

Privileges needed

None

User interaction

Passive

Confidentiality

Low

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-48588.md and follow it. Check whether this project is affected by CVE-2026-48588. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge