Vulnerability · CVE-2023-46695
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.
Published Nov 2, 2023 · catalog updated Jun 17, 2026 · An issue was discovered
Last checked Nov 8, 2026. A connected source was read within the last 7 days.
Check this week
CVE-2023-46695 is not in CISA KEV. FIRST estimates a 53.45% chance of exploitation in the next 30 days. Check whether you run An issue was discovered.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (An issue was discovered).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2026-15920 · Medium
- CVE-2026-15830 · Medium
- CVE-2026-15337 · Medium
- CVE-2026-15307 · High
- CVE-2026-53878 · Medium
- Severity
- High7.5
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 53.45%
- Remediation
- Version ranges on file
- Affected products
- cpe djangoproject/django
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.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- cpe djangoproject/django< 3.2.23
- cpe djangoproject/django< 4.1.13
- cpe djangoproject/django< 4.2.7
How to fix CVE-2023-46695
Upgrade
CVE-2023-46695 lists a fix boundary at 3.2.23. Compare the installed build with that boundary before you change production.
Version check
Affected < 3.2.23
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
CVE-2023-46695 is not in CISA KEV. FIRST estimates a 53.45% chance of exploitation in the next 30 days. Check whether you run An issue was discovered.
Which versions are affected?
Compare what you have installed with < 3.2.23, < 4.1.13, < 4.2.7. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-770: Allocation of Resources Without Limits or Throttling. EPSS 53.45%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Nov 2, 2023 · Monitored products — high
Detected
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.
Jun 17, 2026 · Monitored products — high
Updated
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.
Sources
- CVE.orgVulnerability recordCVE-2023-46695
Official CVE identifier
cve.org - Monitored products — highVendor advisoryCVE-2023-46695
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.
nvd.nist.gov
References
Freshness
Last verified in this catalog Nov 7, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- CVE.orgNov 8, 2026
- Monitored products — highNov 7, 2026