CVE-2026-113593: Potential exposure of private data via empty and missing Vary headers
Noroxi assessment
Priority: Monitor (action score 9/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.46% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No special conditions are required; it is repeatable.
- Fixed version: djangoproject Django 5.2.19, 6.0.10, 6.1.3.
Low priority for now. Upgrade to djangoproject Django 5.2.19, 6.0.10, 6.1.3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Nov 3, 2026
- Updated
- Nov 3, 2026
- EPSS
- 0.4% · 40th percentile
- CWE
- CWE-524
Report tools
Action score
9
Low priority for now.
- CVSS
- 9 / 40 · 2.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · DSF
- 3.1
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (DSF). Independent of NVD's CPE analysis and usually ahead of it.
djangoproject Django
- 6.1.3, 6.0.10, 5.2.19not affected
- 6.1 and later · before 6.1.3affected · python
- 6.0 and later · before 6.0.10affected · python
- 5.2 and later · before 5.2.19affected · python
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.24 | py3-django | before 5.2.19-r0 | 5.2.19-r0 |
| Debian:12 | python-django | before 3:3.2.25-0+deb12u7 | 3:3.2.25-0+deb12u7 |
| Debian:13 | python-django | from 0 | — |
| Debian:14 | python-django | before 3:5.2.19-1 | 3:5.2.19-1 |
| openSUSE:Tumbleweed | python-Django | before 6.1.3-1.1 | 6.1.3-1.1 |
| openSUSE:Tumbleweed | python-Django4 | before 4.2.30-7.1 | 4.2.30-7.1 |
| openSUSE:Tumbleweed | python-Django5 | before 5.2.19-1.1 | 5.2.19-1.1 |
Same product
djangoproject: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-34265An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6.61This week
- CVE-2020-7471Django 1.11 before 1.11.28, 2.2 before 2.2.10, and 3.0 before 3.0.3 allows SQL Injection if untrusted data is used as a StringAgg delimiter…59Plan
- CVE-2019-19844Django before 1.11.27, 2.x before 2.2.9, and 3.x before 3.0.1 allows account takeover.55Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-111211Nov 3, 2026 · Potential log injection via unescaped geometry form values27Monitor
- ← EarlierCVE-2026-111362Nov 3, 2026 · Server-side request forgery via crs member of GeoJSON geometries27Monitor
- Later →CVE-2026-113733Nov 3, 2026 · Password hash disclosure to "view only" admin users with custom user models8Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| djangoproject Django | 5.2.19 | Vendor (CNA) |
| djangoproject Django | 6.0.10 | Vendor (CNA) |
| djangoproject Django | 6.1.3 | Vendor (CNA) |
| alpine:py3-django | 5.2.19-r0 · Alpine:v3.24 | Package registry (OSV) |
| debian:python-django | 3:3.2.25-0+deb12u7 · Debian:12 | Package registry (OSV) |
| debian:python-django | 3:5.2.19-1 · Debian:14 | Package registry (OSV) |
| opensuse:python-Django | 6.1.3-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:python-Django4 | 4.2.30-7.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:python-Django5 | 5.2.19-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 13, 2026+10 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Andrew Gonzalezreporter
- Jake Howardremediation developer
- Sarah Boyceremediation reviewer
- Jacob Wallscoordinator
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-48588119 days apartPotential exposure of private data via cached Set-Cookie response9Monitor
- CVE-2026-35193153 days apartPotential exposure of private data via missing Vary: Authorization in UpdateCacheMiddleware9Monitor
- CVE-2026-6907182 days apartPotential exposure of private data due to incorrect handling of Vary: * in UpdateCacheMiddleware9Monitor
Not on record for this CVE: public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- P
- Scope
- X
Weakness class (CWE)
CWE-524 · Use of Cache Containing Sensitive InformationCVSS vector
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
Change log
- SSVC exploitation— → none
- Exploit maturity— → none
- Fix✗ → ✓
- CVSS3.1 → 2.3
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- github.com/django/django/commit/2006a2b068766bf332f1afcc32b7614d8e5759a2
- github.com/django/django/commit/55e2e009b4f3996e5c55af7b22a8c41eb826e892
- github.com/django/django/commit/9007fecd3633cfd90b093ebe106af564347c8aee
- github.com/django/django/commit/c0b7e5e4e4546e8ddc58262f1945938bb9d9ac2d
- groups.google.com/g/django-announce
- www.djangoproject.com/weblog/2026/nov/03/security-releases/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.