Is CVE-2026-33033 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-33033 being exploited in the wild.

How severe is CVE-2026-33033?

Medium severity, with a CVSS score of 6.5, published 7 April 2026.

Which products and versions are affected?

Django (PyPI) ECOSYSTEM:introduced=4.2,fixed=4.2.30,introduced=5.2,fixed=5.2.13,introduced=6.0,fixed=6.0.4, ECOSYSTEM:introduced=6.0,fixed=6.0.4.

Is there a fix for CVE-2026-33033?

Yes. Django (PyPI): upgrade to 6.0.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-33033 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-33033?

Check whether you run Djangoproject Django or Django (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-33033: Django DoS in MultiPartParser via crafted multipart uploads

CVE-2026-33033 · Severity: medium · CVSS 6.5 · Published 2026-04-07

A vulnerability in the Django web framework could allow an attacker to slow down or crash a website by uploading specially crafted files. By including excessive whitespace in certain parts of a file upload request, an attacker can force the server to spend an enormous amount of processing power on a single request. This can lead to a denial-of-service, making the application unavailable to legitimate users.

Technologies: Djangoproject Django, Django (PyPI). Vendors: Djangoproject, PyPI.

Quick answers

Is CVE-2026-33033 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-33033 being exploited in the wild.
How severe is CVE-2026-33033?: Medium severity, with a CVSS score of 6.5, published 7 April 2026.
Which products and versions are affected?: Django (PyPI) ECOSYSTEM:introduced=4.2,fixed=4.2.30,introduced=5.2,fixed=5.2.13,introduced=6.0,fixed=6.0.4, ECOSYSTEM:introduced=6.0,fixed=6.0.4.
Is there a fix for CVE-2026-33033?: Yes. Django (PyPI): upgrade to 6.0.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-33033 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-33033?: Check whether you run Djangoproject Django or Django (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Django (PyPI): upgrade to 6.0.4 or later
```
pip install "Django>=6.0.4"
```

Technical details

A denial-of-service vulnerability exists in Django's MultiPartParser component due to inefficient algorithmic complexity (CWE-407). When a remote attacker submits a multipart/form-data upload that specifies 'Content-Transfer-Encoding: base64', the parser may experience significant performance degradation if the payload contains excessive whitespace. This occurs because the processing time for such crafted inputs scales poorly, allowing a single request to consume disproportionate CPU resources. The issue is resolved in Django versions 6.0.4, 5.2.13, and 4.2.30. Older unsupported versions like 5.0.x and 3.2.x may also be affected but were not officially evaluated.

Affected products

Django Software Foundation Django >= 6.0, < 6.0.4; >= 5.2, < 5.2.13; >= 4.2, < 4.2.30

Identifiers

CVE-2026-33033
GHSA-5mf9-h53q-7mhq
PYSEC-2026-48

Timeline

2026-04-07: disclosed
2026-04-07: advisory
2026-04-07: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.