Synced 15 Oct 2026 23:44 UTC Account

Is Django 1.3.7 patched?

Django · cycle 1.3 · end of life · Official site ↗
1.3.740/100End of life

Current stable (6.1.2): 100/100

Minimum safe version5.2.17

1.3.7 has 4 open critical-or-high vulnerabilities. Run 5.2.17 or later to clear them. See what 5.2.17 fixes →

Health score40/100
Open issues22
Exploited now0
Cycle 1.3 EOL2013-02-26
Latest release6.1.2

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

Django 1.3.7 is part of the 1.3 release line. 22 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 1.3 line reached end-of-life on 2013-02-26, so it no longer receives security patches. The latest supported Django release is 6.1.2.

Frequently asked

Is Django 1.3.7 patched?

Django 1.3.7 is end-of-life and no longer receives security patches. Move to 6.1.2.

What version should I upgrade Django 1.3.7 to?

Upgrade Django 1.3.7 to at least 5.2.17 to clear its 4 open critical-or-high vulnerabilities.

When does Django 1.3 reach end-of-life?

Django 1.3 reached end-of-life on 2013-02-26 and no longer receives security patches.

What is the latest version of Django?

The latest supported Django release is 6.1.2.

Is Django 1.3.7 still receiving security updates?

No — Django 1.3.7 is on the 1.3 line, which reached end-of-life on 2013-02-26 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 ↗