Django vulnerabilities: known CVEs & security history
Django · Web / Runtime · 150 tracked CVEs · 0 actively exploited · updated June 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Django release lines — 150 in total. A CVE here doesn't mean your version is affected — check Django's current status and the safe version to run.
Known Django CVEs
Actively-exploited and most-severe first. Showing the top 80 of 150. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2026-4277 | critical | 9.8 | 0% | 2026 |
| CVE-2024-53908 | critical | 9.8 | 1% | 2024 |
| CVE-2023-31047 | critical | 9.8 | 1% | 2023 |
| CVE-2022-34265 | critical | 9.8 | 73% | 2022 |
| CVE-2022-28347 | critical | 9.8 | 3% | 2022 |
| CVE-2022-28346 | critical | 9.8 | 18% | 2022 |
| CVE-2021-35042 | critical | 9.8 | 44% | 2021 |
| CVE-2020-7471 | critical | 9.8 | 65% | 2020 |
| CVE-2019-19844 | critical | 9.8 | 35% | 2019 |
| CVE-2019-14234 | critical | 9.8 | 46% | 2019 |
| CVE-2016-9013 | critical | 9.8 | 5% | 2016 |
| CVE-2025-64459 | critical | 9.1 | 19% | 2025 |
| CVE-2014-0474 | high | 10 | 5% | 2014 |
| CVE-2022-36359 | high | 8.8 | 1% | 2022 |
| CVE-2020-9402 | high | 8.8 | 23% | 2020 |
| CVE-2016-9014 | high | 8.1 | 6% | 2016 |
| CVE-2015-5145 | high | 7.8 | 3% | 2015 |
| CVE-2015-5143 | high | 7.8 | 7% | 2015 |
| CVE-2026-3902 | high | 7.5 | 0% | 2026 |
| CVE-2026-33034 | high | 7.5 | 1% | 2026 |
| CVE-2026-25673 | high | 7.5 | 1% | 2026 |
| CVE-2026-1285 | high | 7.5 | 1% | 2026 |
| CVE-2025-14550 | high | 7.5 | 1% | 2026 |
| CVE-2025-64460 | high | 7.5 | 2% | 2025 |
| CVE-2025-64458 | high | 7.5 | 2% | 2025 |
| CVE-2024-53907 | high | 7.5 | 1% | 2024 |
| CVE-2024-45230 | high | 7.5 | 25% | 2024 |
| CVE-2024-41991 | high | 7.5 | 1% | 2024 |
| CVE-2024-41990 | high | 7.5 | 1% | 2024 |
| CVE-2024-41989 | high | 7.5 | 1% | 2024 |
| CVE-2024-39614 | high | 7.5 | 30% | 2024 |
| CVE-2024-38875 | high | 7.5 | 1% | 2024 |
| CVE-2024-24680 | high | 7.5 | 2% | 2024 |
| CVE-2023-43665 | high | 7.5 | 1% | 2023 |
| CVE-2023-41164 | high | 7.5 | 1% | 2023 |
| CVE-2023-46695 | high | 7.5 | 50% | 2023 |
| CVE-2023-36053 | high | 7.5 | 3% | 2023 |
| CVE-2023-24580 | high | 7.5 | 63% | 2023 |
| CVE-2023-23969 | high | 7.5 | 47% | 2023 |
| CVE-2022-41323 | high | 7.5 | 3% | 2022 |
| CVE-2022-23833 | high | 7.5 | 49% | 2022 |
| CVE-2021-45116 | high | 7.5 | 2% | 2022 |
| CVE-2021-45115 | high | 7.5 | 2% | 2022 |
| CVE-2021-33571 | high | 7.5 | 3% | 2021 |
| CVE-2021-31542 | high | 7.5 | 5% | 2021 |
| CVE-2020-24584 | high | 7.5 | 3% | 2020 |
| CVE-2020-24583 | high | 7.5 | 4% | 2020 |
| CVE-2019-14235 | high | 7.5 | 3% | 2019 |
| CVE-2019-14233 | high | 7.5 | 3% | 2019 |
| CVE-2019-14232 | high | 7.5 | 4% | 2019 |
| CVE-2019-6975 | high | 7.5 | 5% | 2019 |
| CVE-2018-6188 | high | 7.5 | 5% | 2018 |
| CVE-2016-7401 | high | 7.5 | 6% | 2016 |
| CVE-2011-0698 | high | 7.5 | 3% | 2011 |
| CVE-2016-2512 | high | 7.4 | 4% | 2016 |
| CVE-2024-42005 | high | 7.3 | 1% | 2024 |
| CVE-2021-44420 | high | 7.3 | 2% | 2021 |
| CVE-2025-59681 | high | 7.1 | 1% | 2025 |
| CVE-2025-57833 | high | 7.1 | 16% | 2025 |
| CVE-2011-4140 | medium | 6.8 | 1% | 2011 |
| CVE-2011-0696 | medium | 6.8 | 2% | 2011 |
| CVE-2026-35192 | medium | 6.5 | 0% | 2026 |
| CVE-2026-33033 | medium | 6.5 | 1% | 2026 |
| CVE-2019-19118 | medium | 6.5 | 2% | 2019 |
| CVE-2019-3498 | medium | 6.5 | 4% | 2019 |
| CVE-2014-1418 | medium | 6.4 | 3% | 2014 |
| CVE-2012-4520 | medium | 6.4 | 4% | 2012 |
| CVE-2022-22818 | medium | 6.1 | 3% | 2022 |
| CVE-2021-32052 | medium | 6.1 | 3% | 2021 |
| CVE-2020-13596 | medium | 6.1 | 3% | 2020 |
| CVE-2019-12308 | medium | 6.1 | 3% | 2019 |
| CVE-2018-14574 | medium | 6.1 | 25% | 2018 |
| CVE-2017-12794 | medium | 6.1 | 24% | 2017 |
| CVE-2017-7234 | medium | 6.1 | 2% | 2017 |
| CVE-2017-7233 | medium | 6.1 | 2% | 2017 |
| CVE-2016-6186 | medium | 6.1 | 6% | 2016 |
| CVE-2014-0482 | medium | 6 | 2% | 2014 |
| CVE-2021-23336 | medium | 5.9 | 37% | 2021 |
| CVE-2020-13254 | medium | 5.9 | 6% | 2020 |
| CVE-2025-27556 | medium | 5.8 | 1% | 2025 |
70 older / lower-severity CVEs not shown — see Django's full record.
Is my Django version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your Django version → · Monitor Django for new CVEs →
Django vulnerabilities — frequently asked
How many known vulnerabilities does Django have?
IsItPatched tracks 150 CVEs for Django. 12 are critical-severity and 47 high-severity. These span every release line — what matters is whether the version you run is affected.
Does Django have any actively-exploited vulnerabilities?
None of Django's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.
What is the most severe Django vulnerability?
Among tracked issues, CVE-2026-4277 (CRITICAL, CVSS 9.8) ranks highest — a Missing authorization weakness.
Is Django safe to use?
It depends on the version. The latest supported Django release (6.0.6) clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Django security status · Django end-of-life · actively-exploited CVEs. Always verify against Django's advisories — see our disclaimer.