CVE-2026-25673: CWE-400: Uncontrolled Resource Consumption in djangoproject Django
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.
AI Analysis
Technical Summary
The vulnerability arises from Django's URLField.to_python() method invoking urllib.parse.urlsplit(), which on Windows platforms performs NFKC Unicode normalization that is disproportionately slow for some Unicode characters. This behavior allows a remote attacker to supply large URL inputs with these characters, leading to excessive resource consumption and denial of service. The affected versions are Django 6.0 before 6.0.3, 5.2 before 5.2.12, and 4.2 before 4.2.29. Unsupported earlier series such as 5.0.x, 4.1.x, and 3.2.x were not evaluated but may also be vulnerable. The CVSS 3.1 base score is 7.5 (high), reflecting network attack vector, low complexity, no privileges or user interaction required, and impact limited to availability.
Potential Impact
An attacker can cause a denial of service by sending specially crafted large URLs containing certain Unicode characters that trigger slow normalization processing on Windows. This leads to uncontrolled resource consumption, potentially degrading or crashing the affected Django application. There is no confidentiality or integrity impact reported.
Mitigation Recommendations
The vulnerability affects Django versions prior to 6.0.3, 5.2.12, and 4.2.29. Applying official patches by upgrading to these fixed versions or later is the recommended mitigation. The Red Hat advisory is available for reference but does not explicitly confirm patch availability; therefore, check the official Django releases for updates. No alternative mitigations or workarounds are specified. Since this is not a cloud service, remediation depends on applying updates.
CVE-2026-25673: CWE-400: Uncontrolled Resource Consumption in djangoproject Django
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.
CVSS v3.1
Score 7.5high
Affected software
pkg:pypi/djangoRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability arises from Django's URLField.to_python() method invoking urllib.parse.urlsplit(), which on Windows platforms performs NFKC Unicode normalization that is disproportionately slow for some Unicode characters. This behavior allows a remote attacker to supply large URL inputs with these characters, leading to excessive resource consumption and denial of service. The affected versions are Django 6.0 before 6.0.3, 5.2 before 5.2.12, and 4.2 before 4.2.29. Unsupported earlier series such as 5.0.x, 4.1.x, and 3.2.x were not evaluated but may also be vulnerable. The CVSS 3.1 base score is 7.5 (high), reflecting network attack vector, low complexity, no privileges or user interaction required, and impact limited to availability.
Potential Impact
An attacker can cause a denial of service by sending specially crafted large URLs containing certain Unicode characters that trigger slow normalization processing on Windows. This leads to uncontrolled resource consumption, potentially degrading or crashing the affected Django application. There is no confidentiality or integrity impact reported.
Mitigation Recommendations
The vulnerability affects Django versions prior to 6.0.3, 5.2.12, and 4.2.29. Applying official patches by upgrading to these fixed versions or later is the recommended mitigation. The Red Hat advisory is available for reference but does not explicitly confirm patch availability; therefore, check the official Django releases for updates. No alternative mitigations or workarounds are specified. Since this is not a cloud service, remediation depends on applying updates.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- DSF
- Date Reserved
- 2026-02-04T18:27:10.657Z
- Cvss Version
- null
- State
- PUBLISHED
- Vendor Advisory Urls
- [{"url":"https://access.redhat.com/security/cve/CVE-2026-25673","vendor":"Red Hat"}]
Threat ID: 69a6f4b6d1a09e29cb4db075
Added to database: 03/03/2026, 14:48:22 UTC
Last enriched: 07/15/2026, 08:40:40 UTC
Last updated: 07/31/2026, 19:22:58 UTC
Views: 323
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.