CISA list

Django versions

Django: update to 6.1.3, 6.0.10 or 5.2.19. 5.1 and older have reached end of life in the lifecycle data.

Data: .

Which Django branch to run

The newest safe release is the newest release of a branch that still gets fixes and that no CVE record we read names as affected.

Which Django branch to run
BranchStatusNewest safe releaseUpgrade to
6.110 CVE records that this page readsBug and security fixes until 30 April 20276.1.36.1.3 (this branch)
6.038 CVE records that this page readsSecurity fixes only until 30 April 20276.0.106.0.10 (this branch)
5.246 CVE records that this page readsSecurity fixes only until 30 April 20285.2.195.2.19 (this branch)
5.112 CVE records that this page readsEnded on 3 December 2025None, the branch has ended5.2.19 (move to 5.2)
5.03 CVE records that this page readsEnded on 2 April 2025None, the branch has ended5.2.19 (move to 5.2)
4.224 CVE records that this page readsEnded on 7 April 2026None, the branch has ended5.2.19 (move to 5.2)
4.1Ended on 1 December 2023None, the branch has ended5.2.19 (move to 5.2)
4.0Ended on 1 April 2023None, the branch has ended5.2.19 (move to 5.2)
3.2Ended on 1 April 2024None, the branch has ended5.2.19 (move to 5.2)
3.1Ended on 7 December 2021None, the branch has ended5.2.19 (move to 5.2)
3.0Ended on 6 April 2021None, the branch has ended5.2.19 (move to 5.2)
2.2Ended on 11 April 2022None, the branch has ended5.2.19 (move to 5.2)
2.1Ended on 2 December 2019None, the branch has ended5.2.19 (move to 5.2)
2.0Ended on 1 April 2019None, the branch has ended5.2.19 (move to 5.2)
1.11Ended on 1 April 2020None, the branch has ended5.2.19 (move to 5.2)
1.10Ended on 2 December 2017None, the branch has ended5.2.19 (move to 5.2)
1.9Ended on 4 April 2017None, the branch has ended5.2.19 (move to 5.2)
1.8Ended on 1 April 2018None, the branch has ended5.2.19 (move to 5.2)
1.7Ended on 1 December 2015None, the branch has ended5.2.19 (move to 5.2)
1.6Ended on 1 April 2015None, the branch has ended5.2.19 (move to 5.2)
1.5Ended on 2 September 2014None, the branch has ended5.2.19 (move to 5.2)
1.4Ended on 1 October 2015None, the branch has ended5.2.19 (move to 5.2)
1.3Ended on 26 February 2013None, the branch has ended5.2.19 (move to 5.2)

Exploited, or likely to be

CVE records for Django that CISA lists as exploited, that have a public exploit, or that EPSS rates 0.50 or more, with the release that fixes each in every branch.

Exploited, or likely to be
RecordSigns of exploitationFixed in
CVE-2025-64459Potential SQL injection via _connector keyword argument in QuerySet and Q objects9.1 Critical · published 5 November 2025Exploit-DB entryFixed in 5.2.8, 5.1.14, 4.2.26

What this page counts

The branches, their dates and the newest release of each are from the product lifecycle data credited under Sources. A later release that a CVE record names as a fix counts as the newest too.

This page reads 50 CVE records that the CVE Numbering Authorities DSF and mitre (as the CVE List names them) published and that name Django. The fixes are from them. A record says a release fixes a flaw when its affected range for a branch ends before that release. A record from any other source gives no version here.

No release of a branch that has ended is called safe here. Some of these branches are still named by records published after they ended.

Sources
  • CVE records: Copyright © 1999-2026, The MITRE Corporation. CVE is a trademark and the CVE logo is a registered trademark of The MITRE Corporation (source). Licence: CVE Program Terms of Use
  • Product lifecycle dates from endoflife.date, Copyright 2020 endoflife.date contributors (MIT License) (source). Licence: MIT License
  • EPSS scores by FIRST (https://www.first.org/epss/), generated by Empirical Security (source)