Skip to content
Fencer Vulns
high 7.5

CVE-2023-46695 in the critical feed json

Django potential denial of service vulnerability in UsernameField on Windows

published 2023-11-02 3 y ago modified 2026-09-08 2 mo ago also BIT-django-2023-46695 , EUVD-2023-0068 , GHSA-qmf9-6jqf-j8fq , PYSEC-2023-222

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
53.4%
EPSS 53.4% chance of exploitation in 30 days, percentile 98%
public exploits
0
none known

Summary

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.

Patch / fix

  • pypi django 3.2.23, 4.1.13, 4.2.7
  • bitnami django 3.2.23, 4.1.13, 4.2.7
  • djangoproject django 3.2.23, 4.1.13, 4.2.7

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2023-46695 updated cvss 7.5

python-django: Potential denial of service vulnerability in UsernameField on Windows

  • Red Hat Storage 3 python-django, python2-django, python-django-bash-completion
    affected: no fix planned “Will not fix”
  • Red Hat Ansible Automation Platform 2 python-django Red Hat OpenStack Platform 16.1 python-django20, python3-django20, python-django20-bash-completion Red Hat OpenStack Platform 16.2 python-django20, python3-django20, python-django20-bash-completion Red Hat OpenStack Platform 17.1 python-django, python3-django Red Hat OpenStack Platform 18.0 python-django Red Hat Satellite 6 python-django, python2-django, python-django-bash-completion
    +1 more products
    Red Hat Update Infrastructure 4 for Cloud Providers python-django
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

53.45% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
OSV 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
pypi django
>=3.2a1, <3.2.23
>=4.1a1, <4.1.13
>=4.2a1, <4.2.7
>=3.2, <3.2.23
>=4.1, <4.1.13
>=4.2, <4.2.7
3.2.23
4.1.13
4.2.7
bitnami django
>=3.2.0, <3.2.23
>=4.1.0, <4.1.13
>=4.2.0, <4.2.7
3.2.23
4.1.13
4.2.7

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption
  • CWE-770 Allocation of Resources Without Limits or Throttling
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.