Potential denial-of-service vulnerability in HttpResponseRedirect and HttpResponsePermanentRedirect on Windows
An issue was discovered in 5.1 before 5.1.14, 4.2 before 4.2.26, and 5.2 before 5.2.8. NFKC normalization in Python is slow on Windows. As a consequence, `django.http.HttpResponseRedirect`, `django.http.HttpResponsePermanentRedirect`, and the shortcut `django.shortcuts.redirect` were subject to a potential denial-of-service attack via certain inputs with a very large number of Unicode characters. 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 Seokchan Yoon for reporting this issue.
- Published
- Nov 5, 2025
- Updated
- Jun 17, 2026
- EPSS
- 1.9% · 79th percentile
- CWE
- CWE-407
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.9%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Affected 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 django4.2 and later · before 4.2.26
- djangoproject django5.1 and later · before 5.1.14
- djangoproject django5.2 and later · before 5.2.8
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
- 5.2.8, 5.1.14, 4.2.26not affected
- 5.2 and later · before 5.2.8affected · semver
- 5.1 and later · before 5.1.14affected · semver
- 4.2 and later · before 4.2.26affected · semver
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 | — |
| PyPI | django | from 4.2 · before 4.2.26 | 4.2.26 |
| PyPI | django | from 5.0a1 · before 5.1.14 | 5.1.14 |
| PyPI | django | from 5.1 · before 5.1.14 | 5.1.14 |
| PyPI | django | from 5.2 · before 5.2.8 | 5.2.8 |
| PyPI | django | from 5.2a1 · before 5.2.8 | 5.2.8 |
| PyPI | django | before 4.2.26 | 4.2.26 |
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 | 4.2.26 | Vendor (CNA) |
| djangoproject Django | 5.1.14 | Vendor (CNA) |
| djangoproject Django | 5.2.8 | Vendor (CNA) |
| PyPI:django | 4.2.26 | Package registry (OSV) |
| PyPI:django | 5.1.14 | Package registry (OSV) |
| PyPI:django | 5.2.8 | 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 | 2025-11-06 |
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+1 d
- TodaySep 30, 2026+329 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.
- Seokchan Yoonreporter
- Jacob Wallsremediation 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.
- CVE-2025-6446027 days apartPotential denial-of-service vulnerability in XML serializer text extraction31Monitor
- CVE-2025-1455090 days apartPotential denial-of-service vulnerability via repeated headers when using ASGI30Monitor
- CVE-2026-128590 days apartPotential denial-of-service vulnerability in django.utils.text.Truncator HTML methods30Monitor
- CVE-2026-33033153 days apartPotential denial-of-service vulnerability in MultiPartParser via base64-encoded file upload26Monitor
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-407 · Inefficient Algorithmic ComplexityCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; 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 helpChange 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/2025/nov/05/security-releases/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.