Advisory

GHSA-7h2m-m8vj-598h

Also known as: BIT-django-2026-35192, CVE-2026-35192, PYSEC-2026-50

Summary

Django Uses Persistent Cookies Containing Sensitive Information

Details

An issue was discovered in 6.0 before 6.0.5 and 5.2 before 5.2.14. Response headers do not vary on cookies if a session is not modified, but SESSION_SAVE_EVERY_REQUEST is True. A remote attacker can steal a user's session after that user visits a cached public page. 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 thanks Cantina for reporting this issue.

Severity

Low Basis: The source's own band: LOW

Dates

Published
2026-05-05 18:33 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

django

PyPI · All systems

Affected

  • introduced 6.0, fixed 6.0.5 (ecosystem)

Fixed versions

6.0.5

Fix

  • Fixed version 6.0.5
    pip install --upgrade django==6.0.5

django

PyPI · All systems

Affected

  • introduced 5.2, fixed 5.2.14 (ecosystem)

Fixed versions

5.2.14

Fix

  • Fixed version 5.2.14
    pip install --upgrade django==5.2.14

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences