Synced 18 Jun 2026 05:58 UTC Account

Is Django 2.0.13 patched?

Django · cycle 2.0 · end of life · Official site ↗
2.0.1340/100End of life

Current stable (6.0.6): 100/100

Health score40/100
Open issues1
Exploited now0
Cycle 2.0 EOL2019-04-01
Latest release6.0.6

Summary iPlain-English security status for Django 2.0.13, built from its CVEs, active-exploitation data, end-of-life date and latest release.

Django 2.0.13 is part of the 2.0 release line. 1 known vulnerability affects it. The 2.0 line reached end-of-life on 2019-04-01, so it no longer receives security patches. The latest supported Django release is 6.0.6.

Known issues affecting 2.0.13

Exploited first, then by exploitation probability.

CVE-2021-33203 MEDIUM EPSS 3% → fixed in 3.2.4

Frequently asked

Is Django 2.0.13 patched?

Django 2.0.13 is end-of-life and no longer receives security patches. Move to 6.0.6.

When does Django 2.0 reach end-of-life?

Django 2.0 reached end-of-life on 2019-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 2.0.13 still receiving security updates?

No — Django 2.0.13 is on the 2.0 line, which reached end-of-life on 2019-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 ↗