CVE-2023-46695
HIGH
7.5
CVSS Score
Published: November 2, 2023 at 12:00 AM UTC
Updated: June 17, 2026 at 06:31 AM UTC
1 product affected across 1 vendorDjango
Using N/A by N/A?
Get instant alerts when new vulnerabilities affect N/A - before attackers find them.
Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 50%
Description
An issue was discovered in Django 3.2 before 3.2.23, 4.1 before 4.1.13, and 4.2 before 4.2.7. The NFKC normalization is slow on Windows. As a consequence, django.contrib.auth.forms.UsernameField is subject to a potential DoS (denial of service) attack via certain inputs with a very large number of Unicode characters.
Affected
Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.
95%
3.2 ≤ v < 3.2.234.1 ≤ v < 4.1.134.2. ≤ v < 4.2.7
Affected range stops below 3.2.23, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.1.13, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.2.7, so it looks safe — our inference, not a vendor statement
Remediation
No guide yetNo remediation guidance has been written for this CVE yet. What the record does show:
References (4)
Permissions Required
Source: [email protected]
https://groups.google.com/forum/#%21forum/django-announcePatchVendor Advisory
Source: [email protected]
https://www.djangoproject.com/weblog/2023/nov/01/security-releases/CVSS
- Attack Vector
- NETWORK
- Complexity
- LOW
- Privileges
- NONE
- User Interaction
- NONE
- Scope
- UNCHANGED
- Confidentiality
- NONE
- Integrity
- NONE
- Availability
- HIGH
Vector?
Quick Info
StatusMODIFIED
CWE
CWE-770
Get alerted
Stop reading CVE feeds looking for your own stack
Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.
Free plan, no card