CVE-2024-24680 is a high-severity (CVSS 7.5) vulnerability in django. A fix is available for django — see the affected versions and patch details below.
Django denial-of-service attack in the intcomma template filter
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-24680.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
django🐍django🐍djangoReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
An issue was discovered in Django 3.2 before 3.2.24, 4.2 before 4.2.10, and Django 5.0 before 5.0.2. The intcomma template filter was subject to a potential denial-of-service attack when used with very long strings.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | django | ≥ 3.2&&< 3.2.24 | 3.2.24pip install --upgrade 'django==3.2.24' |
| 🐍PyPI | django | ≥ 4.2&&< 4.2.10 | 4.2.10pip install --upgrade 'django==4.2.10' |
| 🐍PyPI | django | ≥ 5.0&&< 5.0.2 | 5.0.2pip install --upgrade 'django==5.0.2' |
Affected Products
djangodjangoprojectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for django, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update django to 3.2.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-24680 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Redhat has rated this vulnerability as moderate severity because exploitation of this vulnerability is only theoretical in nature and can only result in a denial of service bug.
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.Source: Red Hat security advisory for CVE-2024-24680 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Ansible Automation Platform 2.4 for RHEL 8 | python3x-django-0:4.2.10-1.el8ap | RHSA-2024:1057 |
| Red Hat Ansible Automation Platform 2.4 for RHEL 8 | automation-controller-0:4.5.5-2.el8ap | RHSA-2024:1640 |
| Red Hat OpenStack Platform 17.1 for RHEL 9 | python-django-0:2.2.24-8.el9ost | RHSA-2024:2731 |
| Red Hat Satellite 6.15 for RHEL 8 | python-django-0:4.2.14-1.el8pc | RHSA-2024:5662 |
| RHUI 4 for RHEL 8 | python-django-0:4.2.11-1.el8ui | RHSA-2024:1878 |
Frequently Asked Questions
Is CVE-2024-24680 in your dependencies?
Find it across PyPI, including transitive dependencies.