Is Django 4.0.10 patched?
Current stable (6.0.6): 100/100
4.0.10 has 2 open critical-or-high vulnerabilities. Run 4.1.13 or later to clear them. See what 4.1.13 fixes →
Summary iPlain-English security status for Django 4.0.10, built from its CVEs, active-exploitation data, end-of-life date and latest release.
Django 4.0.10 is part of the 4.0 release line. 2 known vulnerabilities affect it. The minimum safe version is 4.1.13 — upgrade to it or later to clear the open critical/high issues. The 4.0 line reached end-of-life on 2023-04-01, so it no longer receives security patches. The latest supported Django release is 6.0.6.
Known issues affecting 4.0.10
Exploited first, then by exploitation probability.
CVE-2023-36053 HIGH EPSS 3% → fixed in 4.2.3 CVE-2023-31047 CRITICAL EPSS 1% → fixed in 4.1.9Other Django versions
Check another release line of Django.
Frequently asked
Is Django 4.0.10 patched?
Django 4.0.10 is end-of-life and no longer receives security patches. Move to 6.0.6.
What version should I upgrade Django 4.0.10 to?
Upgrade Django 4.0.10 to at least 4.1.13 to clear its 2 open critical-or-high vulnerabilities.
When does Django 4.0 reach end-of-life?
Django 4.0 reached end-of-life on 2023-04-01 and no longer receives security patches.
What is the latest version of Django?
The latest supported Django release is 6.0.6.
Is Django 4.0.10 still receiving security updates?
No — Django 4.0.10 is on the 4.0 line, which reached end-of-life on 2023-04-01 and no longer receives security updates. Upgrade to 6.0.6 or later to stay supported.
Informational only, from public data (NVD · CISA KEV · EPSS · endoflife.date), and can lag or miss vendor-specific fixes. Always confirm against Django's official advisory before you patch or upgrade — Django official site ↗