Cyber Resilience

CVE-2023-36053

Djangoproject Django 3.2 – 3.2.20

Published
03 July 2023
Modified
04 November 2025
Patch / advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.030 86th percentile
Risk Priority 66 floored blend · peak EPSS

Summary

CVE-2023-36053 is a high-severity Inefficient Regular Expression Complexity (CWE-1333) vulnerability in Djangoproject Django. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked in the top 14% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2023-36053 affects Django versions 3.2 before 3.2.20, 4 before 4.1.10, and 4.2 before 4.2.3. The flaw resides in the EmailValidator and URLValidator classes, which rely on regular expressions that can be forced into catastrophic backtracking when presented with input containing an extremely large number of domain-name labels.

An unauthenticated remote attacker can supply a maliciously crafted email address or URL containing thousands of labels in the domain portion. Because the vulnerable validators perform no length or complexity checks before matching, processing such input consumes excessive CPU time and can render the validating application unresponsive, achieving a denial-of-service condition without any authentication or user interaction.

Official Django security advisories and downstream distribution notices direct users to upgrade immediately to 3.2.20, 4.1.10, or 4.2.3 or later; these releases contain revised validators that limit label count and avoid the expensive regex path. The associated EPSS score has remained essentially flat near 0.1 since disclosure, indicating limited observed exploitation interest to date.

EU & UK References

Vulnerability Data

In Django 3.2 before 3.2.20, 4 before 4.1.10, and 4.2 before 4.2.3, EmailValidator and URLValidator are subject to a potential ReDoS (regular expression denial of service) attack via a very large number of domain name labels of emails and URLs.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
T1499.003 Application Exhaustion Flood Impact
Adversaries may target resource intensive features of applications to cause a denial of service (DoS), denying availability to those applications.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-28755Same product: Debian Debian Linux
CVE-2023-28756Same product: Debian Debian Linux
CVE-2024-27351Same product: Djangoproject Django
CVE-2023-26117Same product: Fedoraproject Fedora
CVE-2023-26118Same product: Fedoraproject Fedora
CVE-2024-25126Same product: Debian Debian Linux
CVE-2024-3772Same product: Fedoraproject Fedora
CVE-2023-30608Same product: Debian Debian Linux
CVE-2024-26146Same product: Debian Debian Linux
CVE-2023-26116Same product: Fedoraproject Fedora

Affected Assets

djangoproject
django
3.2 — 3.2.20 · 4.0 — 4.1.10 · 4.2 — 4.2.3
debian
debian linux
10.0, 11.0, 12.0
fedoraproject
fedora
37, 38

Mitigating Controls

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent inefficient regex via reviews, static analysis, and safe libraries.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover ReDoS issues in existing code but do not stop their introduction.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect and reject regex patterns with exponential worst-case complexity.

prevents

Secure development lifecycle mandates review of algorithmic efficiency, directly addressing ReDoS-prone regex.

prevents

Application security requirements can specify input-validation rules that limit regex complexity.

prevents

Secure architecture principles encourage avoidance of computationally expensive constructs such as catastrophic backtracking.

prevents

Secure coding standards explicitly prohibit or limit the use of inefficient regular expressions.

References