Advisory

PYSEC-2026-54

Also known as: BIT-django-2026-5766, CVE-2026-5766, GHSA-w26r-rmm8-9c29

Summary

The record has no summary.

Details

An issue was discovered in 6.0 before 6.0.5 and 5.2 before 5.2.14.
ASGI requests with a missing or understated Content-Length header can bypass the FILE_UPLOAD_MAX_MEMORY_SIZE limit, potentially loading large files into memory and causing service degradation.

As a reminder, Django expects a limit to be configured at the web server level rather than solely relying on FILE_UPLOAD_MAX_MEMORY_SIZE.
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 Kyle Agronick for reporting this issue.

Severity

Not rated by the source.

Dates

Published
2026-05-05 16:16 UTC
Modified
2026-06-10 17:01 UTC

Affected packages and fixes

django

PyPI · All systems

Affected

  • introduced 5.2, fixed 5.2.14, introduced 6.0, fixed 6.0.5 (ecosystem)

Fixed versions

5.2.14, 6.0.5

Fix

  • Fixed version 5.2.14
    pip install --upgrade django==5.2.14
  • Fixed version 6.0.5
    pip install --upgrade django==6.0.5

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