How severe is CVE-2023-46695?

CVE-2023-46695 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2023-46695?

CVE-2023-46695 affects the following packages: django (PyPI), django (PyPI), django (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2023-46695?

Update django to 3.2.23 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-46695 is resolved across your whole dependency graph.

How do I detect CVE-2023-46695 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for django, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2023-46695 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2023-46695 actively exploited in the wild?

No public exploit code has been indexed for CVE-2023-46695 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2023-46695?

CVE-2023-46695 has an EPSS (Exploit Prediction Scoring System) score of 53.4%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2023-46695?

CVE-2023-46695 is classified as CWE-770 (CWE-770). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2023-46695 published, and has it been updated?

CVE-2023-46695 was published on November 2, 2023 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

HIGH severity

CVE-2023-46695 — django

HIGHFix: django/django@048a9eb

CVE-2023-46695 is a high-severity (CVSS 7.5) CWE-770 vulnerability in django. EPSS puts its 30-day exploitation probability at 53.4% (99th percentile). A fix is available for django — see the affected versions and patch details below.

Django potential denial of service vulnerability in UsernameField on Windows

Also known asBIT-django-2023-46695GHSA-qmf9-6jqf-j8fqPYSEC-2023-222

Published

Nov 2, 2023

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

53.4%probability of exploitation in next 30 days

High Risk+3.67%

Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected

🐍django🐍django🐍django

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

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 Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`django`	≥ 3.2a1&&< 3.2.23	3.2.23`pip install --upgrade 'django==3.2.23'`
🐍PyPI	`django`	≥ 4.1a1&&< 4.1.13	4.1.13`pip install --upgrade 'django==4.1.13'`
🐍PyPI	`django`	≥ 4.2a1&&< 4.2.7	4.2.7`pip install --upgrade 'django==4.2.7'`

Affected Products

1 product · 3 configurations

Application

djangodjangoproject

≥ 4.2. && < 4.2.7

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for django, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update django to 3.2.23 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-46695 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2023-46695 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works