CVE-2025-64458: Potential denial-of-service vulnerability in HttpResponseRedirect and HttpResponsePermanentRedirect on Windows
Noroxi assessment
Priority: Monitor (action score 31/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.9% (FIRST EPSS); higher than 80.1% of all records.
- 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.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: djangoproject Django 4.2.26, 5.1.14, 5.2.8.
Low priority for now. Upgrade to djangoproject Django 4.2.26, 5.1.14, 5.2.8 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 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% · 80th percentile
- CWE
- CWE-407
Report tools
Action score
31
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.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- 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.
| Vendor | Product | CPE |
|---|---|---|
| djangoproject | django | cpe:2.3:a:djangoproject:django |
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
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
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.22 | py3-django | before 4.2.26-r0 | 4.2.26-r0 |
| 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
Published before and after this one in the same product
- ← EarlierCVE-2025-59681Oct 1, 2025 · An issue was discovered in Django 4.2 before 4.2.25, 5.1 before 5.1.13, and 5.2 before 5.2.7.39Monitor
- ← EarlierCVE-2025-59682Oct 1, 2025 · An issue was discovered in Django 4.2 before 4.2.25, 5.1 before 5.1.13, and 5.2 before 5.2.7.26Monitor
- Later →CVE-2025-64459Nov 5, 2025 · Potential SQL injection via _connector keyword argument in QuerySet and Q objects42Plan
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) |
| alpine:py3-django | 4.2.26-r0 · Alpine:v3.22 | Package registry (OSV) |
| 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
- TodayNov 16, 2026+376 d
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-84429335 days apartPotential denial-of-service vulnerability in HTTP header parsing27Monitor
- CVE-2026-33033153 days apartPotential denial-of-service vulnerability in MultiPartParser via base64-encoded file upload26Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · 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 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.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.