CVE-2026-25673

Potential denial-of-service vulnerability in URLField via Unicode normalization on Windows

Published Mar 3, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The vulnerable URLField method in Django calls Python's urllib.parse.urlsplit, which applies NFKC normalization when running on Windows. For certain Unicode characters this normalization is disproportionately slow, allowing a remote attacker to submit a very large URL that consumes excessive CPU time and memory, leading to denial of service. The flaw maps to CWE‑400 (Uncontrolled Resource Consumption) and CWE‑770 (Uncontrolled Resource Consumption).

Affected Systems

The affected product is Django, specifically versions 6.0 before 6.0.3, 5.2 before 5.2.12, and 4.2 before 4.2.29. Earlier unsupported releases such as 5.0.x, 4.1.x and 3.2.x were not evaluated and may also be at risk.

Risk and Exploitability

The CVSS base score of 7.5 indicates high severity. The EPSS score of <1% suggests a low probability of exploitation as of the time of analysis, and the vulnerability is not included in the CISA KEV catalog. Exploitation requires an attacker to send a crafted URL that triggers the slow normalization on a Windows server running Django; the attack vector is remote over the network, inferred from the description.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Django to a fixed release – 6.0.3 or later, 5.2.12 or later, or 4.2.29 or later – depending on your current version.
  • When upgrading is not immediately possible, limit the maximum length or complexity of URLs accepted by the application’s URLField and reject URLs that contain excessive Unicode sequences.
  • Apply request throttling or rate limiting at the application or web‑server layer to reduce the impact of a DoS attempt.

Generated by OpenCVE AI on April 16, 2026 at 14:04 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-8p8v-wh79-9r56 Django vulnerable to Uncontrolled Resource Consumption
History
Type Values Removed Values Added
CPEs cpe:2.3:a:djangoproject:django:*:*:*:*:*:*:*:*
Type Values Removed Values Added
First Time appeared Djangoproject
Djangoproject django
Vendors & Products Djangoproject
Djangoproject django
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title Potential denial-of-service vulnerability in URLField via Unicode normalization on Windows
Weaknesses CWE-400
References
Weaknesses
  • CWE-400

    Uncontrolled Resource Consumption

  • CWE-770

    Allocation of Resources Without Limits or Throttling

Sources

Status
PUBLISHED
Assigner
DSF
Published
Updated
Jul 15, 2026, 1:16 AM
Reserved
Feb 4, 2026, 6:27 PM
Status
Modified
Published
Mar 3, 2026, 3:16 PM
Modified
Jul 15, 2026, 2:18 AM
Severity
Important
Public date
Mar 3, 2026, 2:28 PM