Python versions
Python: update to 3.15.2, 3.14.11, 3.13.18, 3.12.16 or 3.11.18. 3.10 and older have reached end of life in the lifecycle data.
Data: .
Which Python 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. Records whose versions we cannot place on a branch are named at the end of the page.
| Branch | Status | Newest safe release | Upgrade to |
|---|---|---|---|
| 3.153 CVE records | Bug and security fixes until 9 October 2028 | 3.15.2 | 3.15.2 (this branch) |
| 3.1450 CVE records | Bug and security fixes until 1 October 2027 | 3.14.11 | 3.14.11 (this branch) |
| 3.1360 CVE records | Security fixes only until 31 October 2029 | 3.13.18 | 3.13.18 (this branch) |
| 3.1267 CVE records | Security fixes only until 31 October 2028 | 3.12.16 | 3.12.16 (this branch) |
| 3.1165 CVE records | Security fixes only until 31 October 2027 | 3.11.18 | 3.11.18 (this branch) |
| 3.1060 CVE records | Ended on 1 October 2026 | None, the branch has ended | 3.11.18 (move to 3.11) |
| 3.925 CVE records | Ended on 31 October 2025 | None, the branch has ended | 3.11.18 (move to 3.11) |
| 3.810 CVE records | Ended on 7 October 2024 | None, the branch has ended | 3.11.18 (move to 3.11) |
| 3.7 | Ended on 27 June 2023 | None, the branch has ended | 3.11.18 (move to 3.11) |
| 3.6 | Ended on 23 December 2021 | None, the branch has ended | 3.11.18 (move to 3.11) |
| 3.5 | Ended on 30 September 2020 | None, the branch has ended | 3.11.18 (move to 3.11) |
| 3.4 | Ended on 18 March 2019 | None, the branch has ended | 3.11.18 (move to 3.11) |
| 3.3 | Ended on 29 September 2017 | None, the branch has ended | 3.11.18 (move to 3.11) |
| 3.2 | Ended on 20 February 2016 | None, the branch has ended | 3.11.18 (move to 3.11) |
| 2.7 | Ended on 1 January 2020 | None, the branch has ended | 3.11.18 (move to 3.11) |
| 3.1 | Ended on 9 April 2012 | None, the branch has ended | 3.11.18 (move to 3.11) |
| 3.0 | Ended on 27 June 2009 | None, the branch has ended | 3.11.18 (move to 3.11) |
| 2.6 | Ended on 29 October 2013 | None, the branch has ended | 3.11.18 (move to 3.11) |
| 2.5 | Ended on 26 May 2011 | None, the branch has ended | 3.11.18 (move to 3.11) |
| 2.4 | Ended on 19 December 2008 | None, the branch has ended | 3.11.18 (move to 3.11) |
| 2.3 | Ended on 11 March 2008 | None, the branch has ended | 3.11.18 (move to 3.11) |
| 2.2 | Ended on 30 May 2003 | None, the branch has ended | 3.11.18 (move to 3.11) |
| 2.1 | Ended on 9 April 2002 | None, the branch has ended | 3.11.18 (move to 3.11) |
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.
The fixes are from 76 CVE records that the Python Software Foundation's CVE Numbering Authority published and that name Python. 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.
A release gets a page of its own when it fixes three or more CVE records, or any record that CISA lists as exploited or that EPSS rates 0.50 or more, and keeps it. Any other release is a row on its branch page.
Some records give a range with no start: from 0, or before a release. A record is placed on the branch of the release that ends its range. As the record states it, the range also covers every older release. Such a range is not counted when the newest safe release of a branch that still gets fixes is worked out.
A range that holds only pre-releases (alphas, betas and release candidates) is left out. A record whose fix is a release candidate says so in its row, and the release candidate is not listed as a release.
The lifecycle data does not list 3.14.11, the newest release this page gives for 3.14. A CVE record names it as a fix.
9 records are not placed on a branch, so no branch or release row counts them: CVE-2025-15367, CVE-2026-16052, CVE-2026-19552, CVE-2026-19672, CVE-2026-103995, CVE-2026-115559, CVE-2026-115791, CVE-2026-116566 and CVE-2026-124249.
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)