Advisory

PYSEC-2026-49

Also known as: BIT-django-2026-33034, CVE-2026-33034, GHSA-933h-hp56-hf7m

Summary

The record has no summary.

Details

An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30.
ASGI requests with a missing or understated Content-Length header could
bypass the DATA_UPLOAD_MAX_MEMORY_SIZE limit when reading
HttpRequest.body, allowing remote attackers to load an unbounded request body into
memory.
Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank Superior for reporting this issue.

Severity

High Basis: CVSS v3 score 7.5, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Dates

Published
2026-04-07 15:17 UTC
Modified
2026-06-10 17:01 UTC

Affected packages and fixes

django

PyPI · All systems

Affected

  • introduced 4.2, fixed 4.2.30, introduced 5.2, fixed 5.2.13, introduced 6.0, fixed 6.0.4 (ecosystem)

Fixed versions

4.2.30, 5.2.13, 6.0.4

Fix

  • Fixed version 4.2.30
    pip install --upgrade django==4.2.30
  • Fixed version 5.2.13
    pip install --upgrade django==5.2.13
  • Fixed version 6.0.4
    pip install --upgrade django==6.0.4

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: PyPA Advisory Database · CC BY 4.0

Sources & licences