Advisory

PYSEC-2026-2448

Also known as: BIT-django-2026-25673, CVE-2026-25673, GHSA-8p8v-wh79-9r56

Summary

Django vulnerable to Uncontrolled Resource Consumption

Details

An issue was discovered in 6.0 before 6.0.3, 5.2 before 5.2.12, and 4.2 before 4.2.29.

URLField.to_python() in Django calls urllib.parse.urlsplit(), which performs NFKC normalization on Windows that is disproportionately slow for certain Unicode characters, allowing a remote attacker to cause denial of service via large URL inputs containing these characters.

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 Seokchan Yoon 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-07-13 14:36 UTC
Modified
2026-07-13 16:43 UTC

Affected packages and fixes

django

PyPI · All systems

Affected

  • introduced 4.2, fixed 4.2.29, introduced 5.2, fixed 5.2.12, introduced 6.0, fixed 6.0.3 (ecosystem)

Fixed versions

4.2.29, 5.2.12, 6.0.3

Fix

  • Fixed version 4.2.29
    pip install --upgrade django==4.2.29
  • Fixed version 5.2.12
    pip install --upgrade django==5.2.12
  • Fixed version 6.0.3
    pip install --upgrade django==6.0.3

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