Skip to main content
VulnerabilityPublished

CVE-2026-113593: Django · CWE-524

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-113593· Low 3.1

Not known to be exploited · CVSS 3.1 Low · fixed in 6.1.3 : update Django when convenient.

Data as of 3 Nov 2026, 19:31 UTC

CVSS 3.1 base score
3.1Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (DSF)CVSS 3.13.1
CNA (DSF)CVSS 4.02.3
Patch
Available – fixed in 6.1.3, 6.0.10, 5.2.19
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.

What to do

Upgrade Django and django to 6.1.3, 6.0.10 or 5.2.19.

Affected software

ProductAffectedFixed in
DjangodjangoAffected
  • >=6.1 <6.1.3
Fixed in
  • 6.1.3
DjangodjangoAffected
  • >=6.0 <6.0.10
Fixed in
  • 6.0.10
DjangodjangoAffected
  • >=5.2 <5.2.19
Fixed in
  • 5.2.19
PyPIdjangopkg:pypi/djangoOther threatsAffected
  • >=6.1 <6.1.3
  • >=6.0 <6.0.10
  • >=5.2 <5.2.19
Fixed in
  • 6.1.3
  • 6.0.10
  • 5.2.19

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

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

Community reviews

Loading reviews…