Is CVE-2026-35192 exploited in the wild?

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

How severe is CVE-2026-35192?

Medium severity, with a CVSS score of 6.5, published 5 May 2026.

Which products and versions are affected?

Django (PyPI) ECOSYSTEM:introduced=5.2,fixed=5.2.14,introduced=6.0,fixed=6.0.5, ECOSYSTEM:introduced=6.0,fixed=6.0.5.

Is there a fix for CVE-2026-35192?

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

How is CVE-2026-35192 attacked?

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

Am I affected by CVE-2026-35192?

Check whether you run Djangoproject Django or 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-35192: Django session leakage via public cached pages

CVE-2026-35192 · Severity: medium · CVSS 6.5 · Published 2026-05-05

A vulnerability in the Django web framework could allow an attacker to hijack a user's active session. This occurs when a website is configured to save session data on every request and serves public pages through a cache. If a user visits a cached public page, their private session cookie may be inadvertently stored and later served to other visitors, leading to unauthorized account access.

Technologies: Djangoproject Django, Django (PyPI). Vendors: Djangoproject, PyPI.

Quick answers

Is CVE-2026-35192 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-35192 being exploited in the wild.
How severe is CVE-2026-35192?: Medium severity, with a CVSS score of 6.5, published 5 May 2026.
Which products and versions are affected?: Django (PyPI) ECOSYSTEM:introduced=5.2,fixed=5.2.14,introduced=6.0,fixed=6.0.5, ECOSYSTEM:introduced=6.0,fixed=6.0.5.
Is there a fix for CVE-2026-35192?: Yes. Django (PyPI): upgrade to 6.0.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-35192 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-35192?: Check whether you run Djangoproject Django or 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 6.0.5 or later
```
pip install "Django>=6.0.5"
```

Technical details

A session fixation/leakage vulnerability exists in Django when SESSION_SAVE_EVERY_REQUEST is set to True. In affected versions, response headers do not properly vary on cookies if a session is not modified during a request. This can cause downstream caches (like CDNs or local proxies) to store and serve a response containing a specific user's session cookie to other users who request the same public page. An attacker can then use the leaked cookie to impersonate the victim. The issue is fixed in Django 6.0.5 and 5.2.14.

Affected products

Django Software Foundation Django >= 6.0, < 6.0.5
Django Software Foundation Django >= 5.2, < 5.2.14

Identifiers

CVE-2026-35192
GHSA-7h2m-m8vj-598h
PYSEC-2026-50

Timeline

2026-05-05: disclosed
2026-05-05: advisory
2026-05-05: patched

References

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