StackPrism

Is your Django version vulnerable?

Enter your Django version, or paste requirements.txt or pyproject.toml. You get every known advisory for that release, the release that fixes all of them, and how long your line gets security fixes.
Examples:

Result for 5.1.15

Django 5.1.15 has 8 known vulnerabilities

Django 5.1 is past end of life (since Dec 3, 2025): no more security fixes

Move to 5.2.18: it’s on a supported long-term support line.

Fixes all of them
5.2.17
Newest 5.x release
5.2.18 (no known advisories)
Latest release
6.1.2
Supported line to move to
Django 5.2 LTS (5.2.18)

One task with the upgrade and why. Paste it into Claude Code, Cursor or Codex.

Advisories, most urgent first

django 5.1.15 package pageAll Django support dates (opens in a new tab)

Last checked against PyPI, OSV.dev, deps.dev, CISA KEV, FIRST EPSS and endoflife.date.

Django release lines today

Django’s newest release lines, their end of security support from endoflife.date, and whether the newest release in each supported line has known advisories today.

  • Django 6.16.1.2

    Supported until Dec 31, 2027

    Advisories in the newest release: None known

  • Django 6.06.0.9

    Supported until Apr 30, 2027

    Advisories in the newest release: None known

  • Django 5.2 LTS5.2.18

    Supported until Apr 30, 2028

    Advisories in the newest release: None known

  • Django 5.15.1.15

    End of life since Dec 3, 2025

    Advisories in the newest release: No more fixes

  • Django 5.05.0.14

    End of life since Apr 2, 2025

    Advisories in the newest release: No more fixes

Last checked against endoflife.date, PyPI, OSV.dev and deps.dev.

How Django releases are supported

Django marks every .2 feature release, such as 4.2 and 5.2, as long-term support, with security fixes for about three years. Other feature releases get them for a shorter time. The table above shows the exact dates from endoflife.date; Django’s download page has the official schedule.

Moving between patch releases in the same line, say 4.2.11 to the newest 4.2.x, is the cheap fix. Moving to the next LTS line is a bigger job, so start it before your line’s end date.

Where Django advisories come from

Django’s security team announces fixes on its security archive. OSV.dev carries them through the Python Packaging Advisory Database and the GitHub Advisory Database, and the same flaw listed in both is shown once. Each CVE is then looked up in CISA KEV and FIRST EPSS.

Questions

How do I find my Django version?

Run python -m django --version in the app’s environment, or pip show django.

Does it check my other Python packages?

No, this page checks Django. Paste your whole file into the requirements.txt checker or the pyproject.toml checker for every package.

Is my Python version checked?

Not here. The end-of-life checker tells you whether your Python release is still supported, and the file checkers read .python-version.

Can I share a result?

Yes: the address bar holds ?version=…, and opening it runs the check again with today’s data. Result pages aren’t indexed.

Go further than one check

Map your repo into an architecture diagram with live health on every part, get an alert when a new critical finding lands, and hand your coding agent a brief to build from. Free to start.

Map my repoDesign a stack