Potential exposure of private data via whitespace padding in Vary header
An issue was discovered in Django 5.2 before 5.2.15 and 6.0 before 6.0.6. `django.utils.cache.has_vary_header()` in Django does not strip leading or trailing whitespace from `Vary` response header values before comparison, which allows remote attackers to read cached responses via requests to URLs whose responses contain whitespace-padded Vary header values. 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 Navid Rezazadeh for reporting this issue.
- Published
- Jun 3, 2026
- Updated
- Jul 21, 2026
- EPSS
- 0.4% · 35th percentile
- CWE
- CWE-1023
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
9
Monitor
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.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| djangoproject | django | cpe:2.3:a:djangoproject:django |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- djangoproject django5.2 and later · before 5.2.15
- djangoproject django6.0 and later · before 6.0.6
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.0.6, 5.2.15not affected
- 6.0 and later · before 6.0.6affected · python
- 5.2 and later · before 5.2.15affected · python
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | python-django | all versions | — |
| Debian:14 | python-django | before 3:5.2.15-1 | 3:5.2.15-1 |
| openSUSE:Leap 16.0 | python-Django | before 5.2.4-bp160.9.1 | 5.2.4-bp160.9.1 |
| openSUSE:Tumbleweed | python-Django | before 5.2.15-1.1 | 5.2.15-1.1 |
| openSUSE:Tumbleweed | python-Django4 | before 4.2.30-3.1 | 4.2.30-3.1 |
| openSUSE:Tumbleweed | python-Django6 | before 6.0.6-1.1 | 6.0.6-1.1 |
| PyPI | django | from 5.2 · before 5.2.15 | 5.2.15 |
| PyPI | django | from 6.0 · before 6.0.6 | 6.0.6 |
| PyPI | django | from 6.0.0 · before 6.0.6 | 6.0.6 |
| PyPI | django | before 5.2.15 | 5.2.15 |
| SUSE:Linux Enterprise Module for Package Hub 15 SP7 | python-Django | before 4.2.11-150600.3.59.1 | 4.2.11-150600.3.59.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
- CVE-2019-14234An issue was discovered in Django 1.11.x before 1.11.23, 2.1.x before 2.1.11, and 2.2.x before 2.2.4.53Plan
- CVE-2021-35042Django 3.1.x before 3.1.13 and 3.2.x before 3.2.5 allows QuerySet.order_by SQL injection if order_by is untrusted input from a client of a w52Plan
- CVE-2023-24580An issue was discovered in the Multipart Request Parser in Django 3.2 before 3.2.18, 4.0 before 4.0.10, and 4.1 before 4.1.7.49Plan
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.15 | Vendor (CNA) |
| djangoproject Django | 6.0.6 | Vendor (CNA) |
| debian:python-django | 3:5.2.15-1 · Debian:14 | Package registry (OSV) |
| opensuse:python-Django | 5.2.15-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:python-Django4 | 4.2.30-3.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:python-Django6 | 6.0.6-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| PyPI:django | 5.2.15 | Package registry (OSV) |
| PyPI:django | 6.0.6 | Package registry (OSV) |
| suse:python-Django | 4.2.11-150600.3.59.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP7 | 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.
No dated events beyond publication.
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.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Navid Rezazadehreporter
- Jake Howardremediation developer
- Natalia Bidartcoordinator
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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-1023 · Incomplete Comparison with Missing FactorsCVSS 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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- docs.djangoproject.com/en/dev/releases/security/
- groups.google.com/g/django-announce
- www.djangoproject.com/weblog/2026/jun/03/security-releases/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.