Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
cve.newCreate a CVE report
Check your stack
CVE-2026-113593

Potential exposure of private data via empty and missing Vary headers

Products / packages djangoproject Django

Published

Share

Severity and exploitation

Not in CISA KEV

KEV coverage does not rule out exploitation.

KEV checked 15/11/2026, 02:25:31 UTC
DSF · CVSS:3.1 · 3.1
Assessment vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
DSF · CVSS:4.0 · 2.3
Assessment vectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
The headline uses the highest imported catalog score. Assessments can differ by source and CVSS version.

Severity

low3.1

CVSS measures technical severity, not the likelihood of an attack.

Known exploitation

Not listed in the checked CISA KEV catalog

Absence from CISA KEV does not rule out attacks.

Public exploit

Not established by this record

Missing evidence does not mean no public exploit exists.

Remediation

Fix status not established

No structured fix or guidance is available here. Check the latest publisher advisory.

What this means

Django 6.1 before 6.1.3, 6.0 before 6.0.10, and 5.2 before 5.2.19 may expose private data due to identical cache keys for requests with empty or missing headers listed in the Vary header. An attacker with access to the cache may potentially access private data. Earlier Django series may also be affected.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Attack conditions

No attack-condition excerpt has been identified here. Review the full source description and references for authentication, network access, and configuration requirements.

Review supporting sources →

Affected versions

Check the exact model, release, and any platform requirements against your installation.

djangoproject · DSF

Django

6 ranges
DSF version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

6.1 → before 6.1.3

python versions

6.0 → before 6.0.10

python versions

5.2 → before 5.2.19

python versions

unaffected

6.1.3

python versions

6.0.10

python versions

5.2.19

python versions

unknown

Other versions: unaffected

Automatic dependency matching is unavailable for this record. Use the product evidence and publisher’s instructions to check your installation.

What to do

Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.

No structured fix or remediation guidance is available here. Check the full source description and vendor’s latest advisory for a patch or workaround; do not assume another version is safe.

cve.new guidance unless attributed to a publisher. This page does not inspect your installation.

Public exploit evidence

No public exploit reference is identified in the imported evidence. This is not a claim that no exploit exists.

Original source description

Read the full publisher description

An issue was discovered in Django 6.1 before 6.1.3, 6.0 before 6.0.10, and 5.2 before 5.2.19. The django.middleware.cache.UpdateCacheMiddleware and the django.views.decorators.cache.cache_page() decorator generate identical cache keys for requests that omit a header listed in the response’s Vary header and requests that include that header with an empty value, potentially allowing remote attackers to access private data cached for another request. Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected. Django would like to thank Andrew Gonzalez for reporting this issue.

References

7 sources
docs.djangoproject.com/en/dev/releases/security/
Vendor advisoryDSF
django/django · commit c0b7e5e
PatchDSF
django/django · commit 55e2e00
PatchDSF
django/django · commit 2006a2b
PatchDSF
django/django · commit 9007fec
PatchDSF
www.djangoproject.com/weblog/2026/nov/03/security-releases/
Vendor advisoryDSF
View 1 more references
groups.google.com/g/django-announce
Source referenceDSF

Inside the record

Evidence available

Package identity · not supplied
Version evidence
Remediation guidance · not supplied
Weakness classification
Additional publishers

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-113593

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-524 ↗

CWE-524: Use of Cache Containing Sensitive Information

DSF

Related →
Contributing organizations · 2
DSF

Assigning organization

2026-11-03
CISA-ADP

Additional data publisher

2026-11-03

Timeline

All times UTC

  1. Advisory published

    Publication date supplied by the source.

  2. Source updated

    Latest modification date supplied by the source.

  3. Last imported by cve.new

    Latest catalog import, not the date we first saw this advisory.

What changed

Follow changes
  1. CVE · CVE-2026-113593

    Observed 2026-11-03T18:31:56.466Z · upstream updated 2026-11-03T18:26:21.601Z

    Prioritization updated

    before

    []

    after

    [
  {
    "source": "CISA-ADP",
    "type": "SSVC",
    "role": "CISA Coordinator",
    "timestamp": "2026-11-03T17:19:24.284736Z",
    "decisions": [
      {
        "name": "Exploitation",
        "value": "none"
      },
      {
        "name": "Automatable",
        "value": "no"
      },
      {
        "name": "Technical Impact",
        "value": "partial"
      }
    ]
  }
]

Large field values are marked as truncated previews. Original source snapshots remain retained.

Showing up to 50 most recent observed changes.