CVE-2022-23833 is a high-severity (CVSS 7.5) CWE-835 vulnerability in django. EPSS puts its 30-day exploitation probability at 49.5% (99th percentile). A fix is available for django — see the affected versions and patch details below.
Infinite Loop in Django
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2022-23833 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).
Where this sits among everything scored
Of 385,386 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Counts from FIRST.org, log-scaled.
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 MultiPartParser in Django 2.2 before 2.2.27, 3.2 before 3.2.12, and 4.0 before 4.0.2. Passing certain inputs to multipart forms could result in an infinite loop when parsing files.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | django | ≥ 2.2&&< 2.2.27 | 2.2.27pip install --upgrade 'django==2.2.27' |
| 🐍PyPI | django | ≥ 3.2&&< 3.2.12 | 3.2.12pip install --upgrade 'django==3.2.12' |
| 🐍PyPI | django | ≥ 4.0&&< 4.0.2 | 4.0.2pip install --upgrade 'django==4.0.2' |
Affected Products
debian linuxdebiandjangodjangoprojectfedorafedoraprojectDetection & 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 2.2.27 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-23833 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
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.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat OpenStack Platform 16.1 | python-django20-0:2.0.13-18.el8ost | RHSA-2022:8872 |
| Red Hat OpenStack Platform 16.2 | python-django20-0:2.0.13-18.el8ost | RHSA-2022:8853 |
| Red Hat Satellite 6.11 for RHEL 8 | python-django-0:3.2.13-1.el8pc | RHSA-2022:5498 |
Frequently Asked Questions
Is CVE-2022-23833 in your dependencies?
Find it across PyPI, including transitive dependencies.