In Django 3.2 before 3.2.17, 4.0 before 4.0.9, and 4.1 before 4.1.6, the parsed values of Accept-Language headers are cached in order to avo
In Django 3.2 before 3.2.17, 4.0 before 4.0.9, and 4.1 before 4.1.6, the parsed values of Accept-Language headers are cached in order to avoid repetitive parsing. This leads to a potential denial-of-service vector via excessive memory usage if the raw value of Accept-Language headers is very large.
- Published
- Feb 1, 2023
- Updated
- Jun 17, 2026
- EPSS
- 47.4% · 99th percentile
- CWE
- CWE-770
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
44
Plan
Add it to your regular patch cycle.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 14 / 30 · 47.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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 |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux10.0
- djangoproject django3.2 and later · before 3.2.17
- djangoproject django4.0 and later · before 4.0.9
- djangoproject django4.1 and later · before 4.1.6
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:10 | python-django | before 1:1.11.29-1+deb10u6 | 1:1.11.29-1+deb10u6 |
| Debian:12 | python-django | before 3:3.2.17-1 | 3:3.2.17-1 |
| openSUSE:Leap 15.5 | python-Django | before 2.0.7-150000.1.20.1 | 2.0.7-150000.1.20.1 |
| openSUSE:Tumbleweed | python-Django | before 5.1.5-1.1 | 5.1.5-1.1 |
| openSUSE:Tumbleweed | python-Django | before 4.1.6-1.1 | 4.1.6-1.1 |
| PyPI | django | from 3.2 · before 3.2.17 | 3.2.17 |
| PyPI | django | from 3.2a1 · before 3.2.17 | 3.2.17 |
| PyPI | django | from 4.0 · before 4.0.9 | 4.0.9 |
| PyPI | django | from 4.0a1 · before 4.0.9 | 4.0.9 |
| PyPI | django | from 4.1 · before 4.1.6 | 4.1.6 |
| PyPI | django | from 4.1a1 · before 4.1.6 | 4.1.6 |
| Red Hat:rhui:4::el8 | python-django | before 0:3.2.18-1.0.1.el8ui | 0:3.2.18-1.0.1.el8ui |
| Red Hat:rhui:4::el8 | python-future | before 0:0.18.3-1.0.1.el8ui | 0:0.18.3-1.0.1.el8ui |
| Red Hat:rhui:4::el8 | python39-django | before 0:3.2.18-1.0.1.el8ui | 0:3.2.18-1.0.1.el8ui |
| Red Hat:rhui:4::el8 | python39-future | before 0:0.18.3-1.0.1.el8ui | 0:0.18.3-1.0.1.el8ui |
| SUSE:Package Hub 15 SP4 | python-Django | before 2.2.28-bp154.2.6.1 | 2.2.28-bp154.2.6.1 |
| SUSE:Package Hub 15 SP4 | python-Django | before 2.2.28-bp154.2.6.1 | 2.2.28-bp154.2.6.1 |
| SUSE:Package Hub 15 SP5 | python-Django | before 2.2.28-bp155.7.12.1 | 2.2.28-bp155.7.12.1 |
| SUSE:Package Hub 15 SP5 | python-Django | before 2.2.28-bp155.7.3.1 | 2.2.28-bp155.7.3.1 |
| SUSE:Package Hub 15 SP5 | python-Django | before 2.2.28-bp155.7.3.1 | 2.2.28-bp155.7.3.1 |
| SUSE:Package Hub 15 SP5 | python-Django | before 2.2.28-bp155.7.12.1 | 2.2.28-bp155.7.12.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 |
|---|---|---|
| debian:python-django | 3:3.2.17-1 · Debian:12 | Package registry (OSV) |
| opensuse:python-Django | 2.0.7-150000.1.20.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:python-Django | 2.2.28-bp154.2.6.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| PyPI:django | 3.2.17 | Package registry (OSV) |
| PyPI:django | 4.0.9 | Package registry (OSV) |
| PyPI:django | 4.1.6 | Package registry (OSV) |
| red hat:python-django | 0:3.2.18-1.0.1.el8ui · Red Hat:rhui:4::el8 | Package registry (OSV) |
| red hat:python-future | 0:0.18.3-1.0.1.el8ui · Red Hat:rhui:4::el8 | Package registry (OSV) |
| red hat:python39-django | 0:3.2.18-1.0.1.el8ui · Red Hat:rhui:4::el8 | Package registry (OSV) |
| red hat:python39-future | 0:0.18.3-1.0.1.el8ui · Red Hat:rhui:4::el8 | Package registry (OSV) |
| suse:python-Django | 2.2.28-bp154.2.6.1 · SUSE:Package Hub 15 SP4 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2026-06-12 |
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
- First PoC+1226 d
- TodayOct 8, 2026+1344 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.
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.
No credits in the CNA record.
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 user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-770 · Allocation of Resources Without Limits or ThrottlingCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
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)
- FloodingCAPEC-125likelihood: High · Medium
- Excessive AllocationCAPEC-130likelihood: Medium · Medium
- XML Ping of the DeathCAPEC-147likelihood: Low · Medium
- Exponential Data ExpansionCAPEC-197likelihood: High · Medium
- Serialized Data Parameter BlowupCAPEC-229likelihood: High · High
- Serialized Data with Nested PayloadsCAPEC-230likelihood: Medium · High
- Oversized Serialized Data PayloadsCAPEC-231likelihood: Medium · High
- HTTP DoSCAPEC-469Low
ATT&CK techniques
- Network Denial of Service:Direct Network FloodT1498.001
- Network Denial of Service:Reflection AmplificationT1498.002
- Endpoint Denial of ServiceT1499
- Endpoint Denial of Service: OS Exhaustion FloodT1499.001
- Endpoint Denial of Service:Service Exhaustion FloodT1499.002
- Endpoint Denial of Service:Application Exhaustion FloodT1499.003
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- docs.djangoproject.com/en/4.1/releases/security/
- groups.google.com/forum/#%21forum/django-announce
- lists.debian.org/debian-lts-announce/2023/02/msg00000.html
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HWY6DQWRVBALV73BPUVBXC3QIYUM24IK/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LTZVAKU5ALQWOKFTPISE257VCVIYGFQI/
- security.netapp.com/advisory/ntap-20230302-0007/
- www.djangoproject.com/weblog/2023/feb/01/security-releases/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.