cve.bz

CVE-2026-35192 djangoproject django

2.3 lowEPSS 0.5%Fix available

Low (2.3) in djangoproject django. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in django 5.2.14, 6.0.5.

On this page
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.

Severity

CVSS 4.0

2.3 low
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
EPSS
0.5% (unchanged from 0.5% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 46th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-05-05. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-539 Use of Persistent Cookies Containing Sensitive Information
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-35192 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-35192?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-35192?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-35192 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-35192

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-35192](https://cve.bz/cve/badge/CVE-2026-35192.svg)](https://cve.bz/cve/CVE-2026-35192)

HTML:

<a href="https://cve.bz/cve/CVE-2026-35192"><img src="https://cve.bz/cve/badge/CVE-2026-35192.svg" alt="CVE-2026-35192"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
djangoproject Djangofrom 6.0 before 6.0.5
djangoproject Djangofrom 5.2 before 5.2.14

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-7h2m-m8vj-598hPyPIdjango>=6.0 <6.0.56.0.5
GHSA-7h2m-m8vj-598hPyPIdjango>=5.2 <5.2.145.2.14
PYSEC-2026-50PyPIdjango>=5.2 <5.2.14
>=6.0 <6.0.5
5.2.14, 6.0.5

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13python-djangono fix listedDEBIAN-CVE-2026-35192
Debian14python-django3:5.2.14-1DEBIAN-CVE-2026-35192
Ubuntu22.04:LTSpython-django2:3.2.12-2ubuntu1.27UBUNTU-CVE-2026-35192
Ubuntu24.04:LTSpython-django3:4.2.11-1ubuntu1.16UBUNTU-CVE-2026-35192
Ubuntu25.10python-django3:5.2.4-1ubuntu2.5UBUNTU-CVE-2026-35192
Ubuntu26.04:LTSpython-django3:5.2.9-0ubuntu4.1UBUNTU-CVE-2026-35192
UbuntuPro:14.04:LTS, Pro:16.04:LTS, Pro:18.04:LTS and 1 morepython-djangono fix listedUBUNTU-CVE-2026-35192
openSUSETumbleweedpython-Django5.2.14-1.1openSUSE-SU-2026:10718-1
openSUSETumbleweedpython-Django44.2.30-2.1openSUSE-SU-2026:10708-1
openSUSETumbleweedpython-Django55.2.16-1.1openSUSE-SU-2026:11270-1
openSUSETumbleweedpython-Django66.0.5-1.1openSUSE-SU-2026:10709-1
Alpinev3.24py3-django5.2.14-r0ALPINE-CVE-2026-35192

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpine.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

Moderate: A flaw in Django applications, when configured with `SESSION_SAVE_EVERY_REQUEST` enabled, allows for session theft. This occurs because response headers do not properly vary on cookies for unmodified sessions, enabling a remote attacker to steal a user's session after they visit a cached public page. This vulnerability requires a specific configuration and user interaction to be exploited.

Red Hat's mitigation

To mitigate this issue, ensure that the `SESSION_SAVE_EVERY_REQUEST` setting in Django applications is set to `False` unless explicitly required for application functionality. Disabling this setting prevents the vulnerable condition where response headers do not properly vary on cookies for unmodified sessions on cached public pages. Consult your Django application's configuration for specific instructions on modifying this setting. A restart of the Django application or web server may be required for the change to take effect.

ProductPackageStateAdvisory
Red Hat Ansible Automation Platform 2ansible-automation-platform-24/lightspeed-rhel8Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-25/lightspeed-rhel8Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-26/controller-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-26/eda-controller-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-26/gateway-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-26/hub-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-26/lightspeed-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-27/aap-cloud-billing-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-27/controller-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-27/eda-controller-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-27/gateway-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-27/hub-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-27/lightspeed-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-27/metrics-service-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform/automation-dashboard-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-tech-preview/metrics-service-rhel9Fix deferred
Red Hat Ansible Automation Platform 2automation-controllerFix deferred
Red Hat Ansible Automation Platform 2python-djangoFix deferred
Red Hat Discovery 2discovery/discovery-server-rhel9Fix deferred
Red Hat OpenStack Platform 16.2python-django20Fix deferred
7 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-35192.

Attack patterns (CAPEC)

  • CAPEC-21 Exploitation of Trusted Identifiers Likelihood: High · Severity: High
  • CAPEC-31 Accessing/Intercepting/Modifying HTTP Cookies Likelihood: High · Severity: High
  • CAPEC-39 Manipulating Opaque Client-based Data Tokens Likelihood: High · Severity: Medium
  • CAPEC-59 Session Credential Falsification through Prediction Likelihood: High · Severity: High
  • CAPEC-60 Reusing Session IDs (aka Session Replay) Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON