Synced 17 Jun 2026 22:27 UTC Account

Is Django 4.2.30 patched?

Django · cycle 4.2 · end of life · Official site ↗
4.2.3040/100End of life

Current stable (6.0.6): 100/100

Health score40/100
Open issues0
Exploited now0
Cycle 4.2 EOL2026-04-07
Latest release6.0.6

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. No known vulnerabilities affect it in our data. 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.0.6.

Known issues affecting 4.2.30

None found for this version. ✓

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.0.6.

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.0.6.

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.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 ↗