Is Django 4.2.30 patched?
Current stable (6.1.2): 100/100
4.2.30 has 1 open critical-or-high vulnerability. Run 5.2.17 or later to clear it. See what 5.2.17 fixes →
Summary iPlain-English security status for Django 4.2.30, built from its CVEs, active-exploitation data, end-of-life date and latest release.
Django 4.2.30 is part of the 4.2 release line. 3 known vulnerabilities affect it. The minimum safe version is 5.2.17 — upgrade to it or later to clear the open critical/high issues. The 4.2 line reached end-of-life on 2026-04-07, so it no longer receives security patches. The latest supported Django release is 6.1.2.
Known issues affecting 4.2.30
Exploited first, then by exploitation probability.
CVE-2026-15830 MEDIUM EPSS 1% → fixed in 6.0.8 CVE-2026-15307 HIGH EPSS 1% → fixed in 6.0.8 CVE-2026-15337 MEDIUM EPSS 1% → fixed in 6.0.8Other Django versions
Check another release line of Django.
Frequently asked
Is Django 4.2.30 patched?
Django 4.2.30 is end-of-life and no longer receives security patches. Move to 6.1.2.
What version should I upgrade Django 4.2.30 to?
Upgrade Django 4.2.30 to at least 5.2.17 to clear its 1 open critical-or-high vulnerability.
When does Django 4.2 reach end-of-life?
Django 4.2 reached end-of-life on 2026-04-07 and no longer receives security patches.
What is the latest version of Django?
The latest supported Django release is 6.1.2.
Is Django 4.2.30 still receiving security updates?
No — Django 4.2.30 is on the 4.2 line, which reached end-of-life on 2026-04-07 and no longer receives security updates. Upgrade to 6.1.2 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 ↗