CVE-2026-35193: Django UpdateCacheMiddleware May Disclose Private Cached Vulnerability

LOW
Advisory Identifier: GHSA-qpc8-7fxc-cm4p
CVSS 3.1
CWE-524
Published
Advisory Summary

CVE-2026-35193 is a LOW (CVSS 3.1) updatecachemiddleware may disclose private cached vulnerability (CWE-524: Use of Cache Containing Sensitive Information) affecting Django libraries in the PyPI ecosystem. The issue involves updatecachemiddleware may disclose private cached responses by omitting authorization from vary. Remediation is available by upgrading affected packages to version 5.2.15, 6.0.6.

CVE-2026-35193 at a Glance

CVE Identifier CVE-2026-35193
GHSA Identifier GHSA-qpc8-7fxc-cm4p
Severity LOW
CVSS v3.1 Base Score 3.1
CWE Classification CWE-524: Use of Cache Containing Sensitive Information
Affected Product Django
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 3.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-35193

To remediate this vulnerability, upgrade all affected Django dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

django fixed: 5.2.15
pip install django>=5.2.15
django fixed: 6.0.6
pip install django>=6.0.6
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show django

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-35193, inspect your installed packages using pip:

pip show django

Analyze the terminal output to locate any version of Django in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 5.2.15), your application is affected.

Note: The pip show django command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-524: Use of Cache Containing Sensitive Information, where the code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere. In Django, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

An issue was discovered in Django 5.2 before 5.2.15 and 6.0 before 6.0.6. `django.middleware.cache.UpdateCacheMiddleware` in Django does not add `Authorization` to the `Vary` response header for requests bearing that header without `Cache-Control: public`, which allows remote attackers to read private cached responses via unauthenticated requests to the same URL. 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 Shai Berger for reporting this issue.

CVE-2026-35193 Affected Django Versions

2 component(s)
Fixed Versions:
5.2.156.0.6
Product / Package Ecosystem Affected Versions Fixed Version
django
PyPI
≥ 5.2.0
< 5.2.15
5.2.15
django
PyPI
≥ 6.0.0
< 6.0.6
6.0.6

References

Frequently Asked Questions

What is CVE-2026-35193?
CVE-2026-35193 is a security vulnerability in Django involving UpdateCacheMiddleware may disclose private cached responses by omitting Authorization from Vary under CWE-524: Use of Cache Containing Sensitive Information.
Which Django versions are affected?
Affected versions include releases prior to 5.2.15, 6.0.6 across affected packages: django.
What version fixes CVE-2026-35193?
Upgrading to 5.2.15, 6.0.6 (or the latest patched release for your respective branch) resolves the vulnerability.
Is django affected?
Yes, django is affected in releases prior to 5.2.15, 6.0.6. Upgrade your dependency to 5.2.15, 6.0.6 or later.
What is the CVSS score of CVE-2026-35193?
CVE-2026-35193 has a CVSS v3.1 base score of 3.1 (LOW) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N.
What CWE is associated with CVE-2026-35193?
CVE-2026-35193 is classified under CWE-524: Use of Cache Containing Sensitive Information (The code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere.).
How can I check PyPI dependencies for CVE-2026-35193?
Run the dependency tree command: 'pip show django'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-qpc8-7fxc-cm4p",
  "modified" : "2026-08-07T19:55:18Z",
  "published" : "2026-06-03T15:30:42Z",
  "aliases" : [ "CVE-2026-35193" ],
  "summary" : "Django: UpdateCacheMiddleware may disclose private cached responses by omitting Authorization from Vary",
  "details" : "An issue was discovered in Django 5.2 before 5.2.15 and 6.0 before 6.0.6.\n`django.middleware.cache.UpdateCacheMiddleware` in Django does not add `Authorization` to the `Vary` response header for requests bearing that header without `Cache-Control: public`, which allows remote attackers to read private cached responses via unauthenticated requests to the same URL.\nEarlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.\nDjango would like to thank Shai Berger for reporting this issue.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N"
  }, {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "django"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "5.2.0"
      }, {
        "fixed" : "5.2.15"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "django"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "6.0.0"
      }, {
        "fixed" : "6.0.6"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-35193"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/django/django/commit/050a3dc276f9142067260e990e4d8d42d5e32863"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/django/django/commit/664652f1a2dd80d8a4cd491b4313cad915ae6669"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/django/django/commit/a2faa8e895926ac5d63f72879b5ccf671b5b4ba9"
  }, {
    "type" : "WEB",
    "url" : "https://docs.djangoproject.com/en/dev/releases/security"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2026-197.yaml"
  }, {
    "type" : "WEB",
    "url" : "https://groups.google.com/g/django-announce"
  }, {
    "type" : "WEB",
    "url" : "https://www.djangoproject.com/weblog/2026/jun/03/security-releases"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-524" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-07T19:55:18Z",
    "nvd_published_at" : "2026-06-03T14:16:41Z"
  }
}