CVE-2024-41990: Django Denial-of-Service Vulnerability
Summary
CVE-2024-41990: Django vulnerable to a denial-of-service attack. Affects django across 2 version ranges.
>= 4.2, < 4.2.15
>= 5.0, < 5.0.8
Fixed in 4.2.15 or 5.0.8, depending on the release line you run. How to fix ↓
Also tracked for
- django · Bitnami
- python-django · Debian:11
The same CVE-2024-41990 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Django is a popular Python web framework that provides a set of tools and libraries for building web applications. It is widely used due to its simplicity, scalability, and security features. However, Django versions 5.0 before 5.0.8 and 4.2 before 4.2.15 are vulnerable to a denial-of-service attack. This vulnerability affects the 'urlize()' and 'urlizetrunc()' template filters when processing very large inputs with a specific sequence of characters.
Vulnerability Detail
The vulnerability in Django allows an attacker to launch a denial-of-service attack by exploiting the 'urlize()' and 'urlizetrunc()' template filters. By providing very large inputs with a specific sequence of characters, an attacker can cause the application to consume excessive resources, leading to a denial of service. This can impact the availability and performance of the affected Django application.
How To Fix
Latest published version: 6.1.2 as of 22 Oct 2026
pip install --upgrade "django==6.1.2"Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
>= 4.2, < 4.2.154.2.15pip install --upgrade "django==4.2.15" -
>= 5.0, < 5.0.85.0.8pip install --upgrade "django==5.0.8"
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
There is no known workaround for this vulnerability. It is essential to apply the recommended fix by upgrading Django to the patched versions.
Conclusion
Django versions 5.0 before 5.0.8 and 4.2 before 4.2.15 are vulnerable to a denial-of-service attack. Upgrading to the patched versions is crucial to mitigate this vulnerability and ensure the proper functioning of the 'urlize()' and 'urlizetrunc()' template filters.
See every vulnerability recorded for django →
FAQ
This vulnerability can lead to a denial-of-service attack, causing the affected Django application to consume excessive resources and potentially impacting its availability and performance.
Django versions 5.0 before 5.0.8 and 4.2 before 4.2.15 are affected by this vulnerability.
You can check the version of Django in your application by running the command 'python -m django --version' in your terminal.
At the time of this advisory, there are no known public exploits specifically targeting this vulnerability.
Yes, the CVSS score for this vulnerability is 5.3 (Moderate).
References
Related vulnerabilities
Recent vulnerabilities recorded for django.
