CVE-2026-35192 Session fixation via public cached pages and SESSION_SAVE_EVERY_REQUEST
Attackers can hijack user sessions via cached public pages when SESSION_SAVE_EVERY_REQUEST is enabled, requiring an upgrade to patched Django versions.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-35192?
CVE-2026-35192 is a low-severity authentication bypass vulnerability in Djangoproject Django, published on 5 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
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 would like to thank Cantina for reporting this issue.
Weakness: CWE-539
Which versions are affected by CVE-2026-35192?
6 open source packages ship an affected version, including django and Django. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
django Bitnami | From 5.2.0 | 5.2.14, 6.0.5 |
django PyPI | From 5.2 | 5.2.14, 6.0.5 |
django PyPI | From 5.2 | 5.2.14 |
django PyPI | From 6.0 | 6.0.5 |
Django PyPI | From 5.2 | 5.2.14 |
Django PyPI | From 6.0 | 6.0.5 |
Products include Djangoproject Django.
How do I fix CVE-2026-35192?
Upgrade django to a fixed version for your release line: 5.2.14 or 6.0.5.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2026-35192 being exploited?
There is no known exploitation of CVE-2026-35192 in the wild and no public exploit code.
Other vulnerabilities in Djangoproject Django
- CVE-2026-4277 Privilege abuse in GenericInlineModelAdmin
- CVE-2024-53908 Django SQL injection in HasKey(lhs, rhs) on Oracle
- CVE-2024-42005 Django SQL injection vulnerability
- CVE-2023-31047 Django bypasses validation when using one form field to upload multiple files
- CVE-2022-34265 Django `Trunc()` and `Extract()` database functions vulnerable to SQL Injection
Sources
Also known as BIT-django-2026-35192, DEBIAN-CVE-2026-35192, ECHO-da14-670e-14a1, GHSA-7h2m-m8vj-598h, MINI-5j3x-hf53-99p6, PYSEC-2026-50.