CVE-2026-48588: Django: cache middleware may expose private responses when unrelated request cookies are present

Low CVSS 3.1

OSV id
GHSA-3h9f-r86x-qvjx
Also known as
BIT-django-2026-48588, CVE-2026-48588, PYSEC-2026-2090
Published
Last modified

Affected packages

PackageAffected versionsFixed in
django
PyPI
< 5.2.16 5.2.16
django
PyPI
>= 6.0.0, < 6.0.7 6.0.7

Versions we track that it affects: django 5.0.6, django 4.2.11; django 5.0.6, django 4.2.11

How to fix it

django (PyPI)

Upgrade django to 5.2.16 or later.

# in requirements.txt: change the line to django==5.2.16
pip install -r requirements.txt
  • If it is an indirect dependency, upgrade the package that depends on it, or add a minimum version constraint for it (e.g. in constraints.txt, or as a dependency in pyproject.toml).
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

django (PyPI)

Upgrade django to 6.0.7 or later.

# in requirements.txt: change the line to django==6.0.7
pip install -r requirements.txt
  • If it is an indirect dependency, upgrade the package that depends on it, or add a minimum version constraint for it (e.g. in constraints.txt, or as a dependency in pyproject.toml).
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

Not sure whether your project uses an affected version? Check your lockfile below for free.

Details

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.

References

Am I affected?

Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About this data

Source: GitHub Advisory Database via OSV.dev (CC-BY 4.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.