All reports
High

Resource exhaustion in Django

Affected versions

Version ranges need review.

Affected versions
>=3.2 <3.2.18 || >=4.0 <4.0.10 || >=4.1 <4.1.7
Fixed version
3.2.18 · 4.0.10 · 4.1.7
Affected versions
>= 3.2a1, < 3.2.18
Fixed version
3.2.18
Affected versions
>= 4.1a1, < 4.1.7
Fixed version
4.1.7
Affected versions
>= 4.0a1, < 4.0.10
Fixed version
4.0.10
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2023-24580

Probability of exploitation in the next 30 days: 62.58%

FIRST EPSS · 2026-11-19

Description

An issue was discovered in the Multipart Request Parser in Django 3.2 before 3.2.18, 4.0 before 4.0.10, and 4.1 before 4.1.7. Passing certain inputs (e.g., an excessive number of parts) to multipart forms could result in too many open files or memory exhaustion, and provided a potential vector for a denial-of-service attack.

Links

Credits

  • RamonvdW
  • sunSUNQ