Skip to main content
BumbleTap
Add to ChromeInstall

Python 3.13 End of Life (EOL): October 2029, and What Security-Only Means Now

Python 3.13 stopped getting bug fixes and installers in October 2026. It gets source-only security fixes until October 2029, so nothing forces a move yet. Python 3.14 is the version to move to.

Written Shahzeb Umer

Subscribe

Status

Supported

Support ends .

Time left
1077 days
Latest release
3.13.18
Move to
Python 3.14fixed until Oct 2030

5.1 years of support

  • Bug and security fixes7 Oct 2024 – 1 Oct 2026
  • Security fixes only1 Oct 2026 – Oct 2029

Supported for 5.1 years, from 7 Oct 2024 to Oct 2029.

Who still patches it

Nine places Python 3.13 runs, seven deadlines.

  • python.org (upstream, source only): Security fixes to Oct 2029
  • python.org installers (Windows and macOS): Last one 3.13.17, 21 Oct 2026
  • Amazon Linux 2023 (python3.13): Patched to 30 Jun 2029
  • AWS Lambda (python3.13): Updates blocked 31 Aug 2029
  • Azure Functions (Python 3.13): Support ends Oct 2029
  • Cloud Run functions (python313): Decommissioned 10 Apr 2030
  • Debian 13 (python3, default): LTS to 30 Jun 2030, paid to Jun 2035
  • Heroku (Python buildpacks): Supported, no end announced
  • Docker image (python:3.13, Linux): Still rebuilt, no end announced
Sources: python.org, Amazon Linux 2023 package list, AWS Lambda runtimes, Azure Functions supported languages, Cloud Run functions runtime support, Debian release and LTS pages, Heroku Dev Center, docker-library official images. Checked 17 Nov 2026.

Where to move

Be on Python 3.14.

The short version

  • Python 3.13 reaches end of life in October 2029, five years after 3.13.0 came out on 7 October 2024. Since 3.13.16 on 1 October 2026 it is security-only: no more bug fixes, and releases as source code with no Windows or macOS installers. The latest is 3.13.18, from 25 October 2026.
  • The platforms keep it until 2029. AWS Lambda deprecates python3.13 on 30 June 2029, Azure Functions and Google end it in October 2029, and Debian 13, where it is the default python3, patches it until 30 June 2030. Free-threaded 3.13 is the exception: NumPy, SciPy, pandas and PyTorch stopped publishing cp313t wheels in June 2026.
  • Move to Python 3.14 at your next planned upgrade, ideally before October 2027, when SPEC 0 lets scientific libraries drop 3.13. It runs everywhere 3.13 does and gets security fixes until October 2030. 3.15 adds a year but is still a preview on Lambda, Azure Functions and Google Cloud. TensorFlow users wait: its stable release has no 3.14 wheels.
On this page
  1. What security-only means in practice
  2. What is still fine
  3. Who still patches Python 3.13
  4. Free-threaded 3.13 was the experiment
  5. How to check what you run
  6. Should you move now, and to what?
  7. What the move from 3.13 to 3.14 involves
  8. If you stay on 3.13 for now
  9. Sources

Python 3.13 reaches end of life in October 2029. PEP 719, the 3.13 release schedule, and python.org's devguide give the month and no day: the day is whenever the final 3.13 release ships. After that, python.org makes no further changes to the 3.13 branch.

The change that matters today came earlier. On 1 October 2026, two years after 3.13.0, python.org published 3.13.16, the last regular bugfix release, and moved 3.13 into the security phase. It still gets fixes for vulnerabilities, published as source code when they are needed, and nothing else.

Your 3.13 code runs the same as it did in September. What changed is which fixes reach you and in what form, and that depends on where your interpreter came from. This page covers what the security phase changes, who still patches 3.13, and whether to move to Python 3.14 or 3.15.

What security-only means in practice

python.org's devguide puts it in one sentence: in the security phase "only security fixes are accepted and no more binaries are released. New source-only versions can be released as needed." For 3.13 that played out within a month.

Bug fixes stopped with 3.13.16, on 1 October 2026. It carried around 290 bug fixes, build improvements and documentation changes, and python.org called it "the last full maintenance release". A crash or wrong result found in 3.13 from now on is fixed in 3.14 and later only, unless it is a security issue.

Installers stopped with 3.13.17, on 21 October 2026. That release was an exception. It shipped pip 26.2.2, with updated certificates, after the eMudhra and emSign certificate authority incident, and python.org built installers for it because "3.13 only just entered security-only mode". Four days later 3.13.18 came out as source only, under the heading "No installers".

3.13.18 is the release Windows and macOS installs miss. It makes the ssl module reject the compromised eMudhra intermediate CA keys, updates the bundled Expat to 2.9.0, closes a bypass of tarfile's tar filter, and fixes CVE-2024-3220, which stops mimetypes reading the system's known-files list by default on Windows: a Windows-only fix that no Windows installer carries.

What follows from that:

  • A python.org install on Windows or macOS stays at 3.13.17. No newer installer will be built, so later security fixes never reach it.
  • The bundled OpenSSL freezes with it. python.org's Windows and macOS builds carry their own OpenSSL, which 3.13.16 moved from 3.0.21 to 3.5.9, in the 3.5 LTS series. A later OpenSSL fix reaches those builds only through a new installer.
  • CI splits by platform. actions/setup-python has 3.13.18 for Linux only, so a python-version: "3.13" job gets 3.13.18 on Ubuntu runners and 3.13.17 on Windows and macOS.
  • Docker dropped the Windows images. The official python image removed its 3.13 Windows Server variants in the 3.13.18 update on 25 October 2026. The Linux tags, built from source on Debian 13, Debian 12 and Alpine, are at 3.13.18.

uv is the way round it on a desktop. Its managed Python comes from the python-build-standalone project, which built 3.13.18 for Windows and macOS on 26 October 2026, so an up-to-date uv installs it with uv python install 3.13.

Security fixes continue until October 2029, "irregularly on an as-needed basis", in PEP 719's words. The pace so far has not been slow: 3.13.16 fixed eight CVEs in ssl, tarfile, zipfile, urllib.request and the StringPrep code, and the two releases after it answered the certificate incident within a week of each other.

What is still fine

Nothing in 3.13 switches off, and no major platform drops it before mid-2029. An interpreter built from python.org's source gets every security fix as it ships, and that covers the Linux Docker images and pyenv and uv builds. Managed platforms patch their own runtimes: Heroku supports only the latest 3.13 patch release, and AWS, Microsoft and Google keep patching theirs until the dates below.

What you give up is the smaller fixes. A bug you hit in 3.13 now stays in 3.13, and the workaround lives in your code until you move.

Who still patches Python 3.13

Where your interpreter came from decides whose dates apply. python.org's date covers interpreters built from upstream source. A distribution patches its own package on its own schedule.

Where it runs Until What happens after Source
python.org source releases October 2029, security fixes only Branch frozen, no more releases devguide
python.org Windows and macOS installers Ended with 3.13.17, 21 October 2026 No newer installer will be built 3.13.18
Amazon Linux 2023, python3.13 package 30 June 2029, when AL2023 itself ends No further updates; the system python3 stays 3.9 AWS
AWS Lambda, python3.13 Deprecated 30 June 2029 Create blocked 31 July, updates blocked 31 August 2029; invocations continue AWS
Azure Functions, Python 3.13 October 2029 (expected) Apps keep running with no fixes or patches from Microsoft. Not offered on the Linux Consumption plan, where 3.12 is the last version Microsoft
Google Cloud Run functions, python313 Deprecated 10 October 2029 Decommissioned 10 April 2030: no deploys or updates, and functions may be disabled Google Cloud
Google App Engine standard, python313 End of support 10 October 2029 No patches, no new deployments or updates; apps keep serving. Deprecated 10 October 2030 Google Cloud
Heroku Python buildpacks Supported, latest patch release only No date yet; Heroku deprecates versions as they approach python.org's end of life Heroku
Debian 13, python3 (3.13.5) 30 June 2030, by Debian LTS Freexian sells Extended LTS for Debian 13 to 30 June 2035 Debian
Fedora 43, 44 and 45, EPEL 9 and 10, python3.13 Packaged at 3.13.18 An extra interpreter, not the default python3 in any supported Fedora Fedora
Docker image python:3.13 Linux tags rebuilt as 3.13.18 Windows Server tags removed 25 October 2026; no end announced for Linux official-images

Debian 13 is the long tail. Debian 13 "trixie", released on 9 August 2025, ships 3.13 as its default python3. So does openSUSE Leap 16.0, whose release notes say a future minor version is likely to move to a newer Python. The Debian security team supports trixie until 9 August 2028 and Debian LTS until 30 June 2030, eight months past python.org's date. python3 --version prints 3.13.5, because Debian backports fixes instead of moving to new upstream releases; the package is at 3.13.5-2+deb13u5.

Distribution support is not a promise of speed. As of 17 November 2026, Debian's security tracker lists 23 open python3.13 issues for trixie, including all eight CVEs that 3.13.16 fixed upstream on 1 October. It marks 21 of them as not warranting a security advisory, which Debian says can still be fixed in a point release, and three of those as ignored.

python:3.13-trixie is not Debian's Python. The official Docker image downloads python.org's source and compiles it on a Debian base. Debian patches the operating system layer and python.org's releases patch the interpreter, which is why the image is at 3.13.18 while Debian's package is at 3.13.5.

Ubuntu and Red Hat skipped 3.13. No supported Ubuntu release ships it: 22.04 has 3.10, 24.04 has 3.12, and 26.04 and 26.10 have 3.14. RHEL 10's full-life Python is 3.12, and RHEL 9.8 and 10.2 added a Python 3.14 stream without a 3.13 one. Alpine went from 3.12 in 3.23 to 3.14 in 3.24. Fedora 43 and 44 use 3.14 and Fedora 45 uses 3.15, keeping python3.13 as an extra package.

Free-threaded 3.13 was the experiment

3.13 introduced the free-threaded build, an interpreter without the global interpreter lock (GIL), shipped as a separate executable usually called python3.13t. python.org labelled it experimental and told users to "expect some bugs and a substantial single-threaded performance hit". python -VV on a 3.13t build says "experimental free-threading build".

In 3.14 the build became officially supported, under PEP 779, with the single-threaded slowdown down to roughly 5 to 10%. The libraries followed it there. NumPy 2.5.0, SciPy 1.18.0, pandas 3.0.4 and PyTorch 2.12.1, all released in June 2026, dropped cp313t wheels, and all four publish cp314t wheels. On 3.13t, pip now builds their current releases from source.

If you are trying free-threading on 3.13t, move that work to 3.14t. It is the first version where the build is supported, and the one the libraries build for.

How to check what you run

The interpreter on your PATH, the one your service runs and the one CI uses can all differ.

python3 --version
python3 -VV                         # a free-threaded 3.13 says "experimental free-threading build"
python3 -c 'import sys; print(sys.version); print(sys.executable)'
which -a python3 python3.13 python3.13t
uv python list --only-installed     # if you use uv
apt-cache policy python3.13         # Debian 13: installed and candidate versions

In your repositories:

grep -rnE --include='Dockerfile*' --include='Containerfile*' 'FROM .*python:3\.13' .
grep -rnE 'python-version:.*3\.13' .github/workflows/
grep -nE 'requires-python|python_requires' pyproject.toml setup.cfg setup.py 2>/dev/null
cat .python-version runtime.txt 2>/dev/null

On your platforms:

# AWS Lambda: once per region and per account
aws lambda list-functions --function-version ALL --region us-east-1 --output text \
  --query "Functions[?Runtime=='python3.13'].FunctionArn"

# Azure Functions on Linux: prints Python|3.13 for a 3.13 app
az functionapp config show --name APP --resource-group RG --query linuxFxVersion --output tsv

To see whether your pinned dependencies already have wheels for 3.14, ask pip to resolve them without installing anything:

python3 -m pip download -r requirements.txt --only-binary=:all: --python-version 3.14 --no-deps -d /tmp/wheels-314

Should you move now, and to what?

3.13 3.14 3.15
First release 7 Oct 2024 7 Oct 2025 9 Oct 2026
Bugfix releases and installers Ended Oct 2026 Until about Oct 2027 Until about Oct 2028
Security fixes until Oct 2029 Oct 2030 Oct 2031
Latest, 17 Nov 2026 3.13.18 3.14.10 3.15.2
AWS Lambda Deprecated 30 Jun 2029 Deprecated 30 Jun 2029 Preview
Azure Functions Expected end Oct 2029 Expected end Apr 2029 Preview
Cloud Run functions Deprecated 10 Oct 2029 Deprecated 10 Oct 2030 Preview
Free-threaded build Experimental Supported Supported
No wheels yet from None of the big packages TensorFlow (stable) TensorFlow, ONNX Runtime, Ray, PyYAML
Default python3 in Debian 13, openSUSE Leap 16.0 Ubuntu 26.04, Fedora 43 and 44, Alpine 3.24 Fedora 45

Nothing forces a move yet. Lambda gives python3.13 and python3.14 the same deprecation date, 30 June 2029, the end of Amazon Linux 2023. Azure expects to end 3.14 in April 2029, six months before 3.13; its policy ends a version at the earlier of python.org's date and its base operating system's. Only Google gives 3.14 an extra year. The pressure comes from libraries instead. SPEC 0, the Scientific Python ecosystem's support policy, recommends dropping 3.13 from 7 October 2027, and Django says Django 2028 will support only 3.14, 3.15 and 3.16.

Target 3.14. It is generally available on Lambda, Azure Functions, Cloud Run functions, App Engine and Heroku, and it is the default python3 in Ubuntu 26.04 LTS. NumPy, pandas, SciPy, scikit-learn, PyTorch, pydantic-core, psycopg-binary, ONNX Runtime and Ray all publish 3.14 wheels. It gets bug fixes until about October 2027, which makes the next year the best time to move: after that, 3.14 is security-only too, and 3.15 becomes the better target.

TensorFlow is the exception. Its stable release, 2.21.0 from 6 March 2026, publishes wheels up to 3.13 only. 2.22.0rc1, from 16 November 2026, adds 3.14. If you depend on TensorFlow, stay on 3.13 until 2.22 is final.

3.15 is fine where the platform allows it. It adds a year of security fixes, gets bug fixes until about October 2028, and Heroku already uses it for new apps. But Lambda, Azure Functions, Cloud Run functions and App Engine all list it as a preview, and AWS says preview runtimes "should not be used for production workloads"; its target for general availability is November 2026. ONNX Runtime 1.32.0, Ray 2.60.0 and PyYAML 6.0.3 publish no 3.15 wheels yet. 3.15 also makes UTF-8 the default encoding for files opened without one, which changes behaviour wherever the locale encoding is not UTF-8. For a container with every wheel available, it is a reasonable jump straight from 3.13.

What the move from 3.13 to 3.14 involves

Most 3.13 code runs on 3.14 unchanged, and the jump is smaller than from 3.11 or 3.12. The changes that bite are covered in detail on the Python 3.14 page:

  • asyncio.get_event_loop() raises RuntimeError when there is no current event loop, instead of creating one.
  • multiprocessing and ProcessPoolExecutor start workers with forkserver on Linux, not fork.
  • tarfile extracts with the data filter by default and refuses links outside the destination.
  • Annotations are evaluated lazily (PEP 649), which matters to code and libraries that read __annotations__ themselves.
  • APIs deprecated since 3.12 are gone, among them ast.Num and ast.Str, pkgutil.find_loader(), the asyncio child watchers, and urllib.request.URLopener.

Most of what 3.14 removed already warns on 3.13, so start there:

python3.13 -W error::DeprecationWarning -m pytest

Then add 3.14 to CI next to 3.13 and run the same command. Much of the work usually turns out to be in dependencies, so bump them first.

If you stay on 3.13 for now

Keep taking the source releases. On Linux, rebuild Docker images regularly and keep pyenv or uv builds current. 3.13 is supported, but only for the copies that get updated.

Get off python.org's installer on Windows and macOS. It stops at 3.13.17. uv's managed 3.13.18, or the Linux image in a container, keeps you on security fixes.

Use a distribution build if you want a security team behind it. Debian 13's python3 is 3.13 and Debian LTS patches it until 30 June 2030, at the cost of Debian's 3.13.5-based package and its packaging rules.

Write down the date you are deferring to, and put it somewhere that gets read. Python 3.11 shows how the squeeze goes for a security-only version, and Python 3.10 what happens once it ends. The Python hub has every version's dates.

Sources

Common questions

When is Python 3.13 end of life?
In October 2029, five years after 3.13.0 came out on 7 October 2024. python.org commits to the month only; the exact day becomes known when the final 3.13 release ships. Until then 3.13 gets security fixes, released as source code when needed.
Is Python 3.13 still supported?
Yes, for security fixes only, until October 2029. Regular bug fixes ended with 3.13.16 on 1 October 2026, and the last python.org Windows and macOS installers came with 3.13.17 on 21 October 2026. The latest release, 3.13.18 from 25 October 2026, is source only.
What does security-only mean for Python 3.13?
python.org accepts only security fixes into the 3.13 branch and publishes them as source code, when needed, with no new installers or binaries. A bug found in 3.13 from now on is fixed in 3.14 and later only, unless it is a security issue. Builds from source, such as the Linux Docker images, pyenv and uv, keep getting every fix.
How do I get Python 3.13.18 on Windows or macOS?
Not from python.org, which built no installers for it; its installers stop at 3.13.17. uv's managed Python comes from the python-build-standalone project, which published 3.13.18 for Windows and macOS on 26 October 2026, so an up-to-date uv gets it with uv python install 3.13. actions/setup-python has 3.13.18 for Linux only.
When is Python 3.12 end of life?
October 2028. 3.12 has been security-only since 3.12.10 on 8 April 2025, and its latest release is 3.12.16, from 25 October 2026. It is Ubuntu 24.04 LTS's default python3 and RHEL 10's full-life Python stream. AWS Lambda deprecates its python3.12 runtime on 31 October 2028 and blocks updates to python3.12 functions from 10 January 2029.
Should I upgrade Python 3.13 to 3.14 or 3.15?
3.14 for most projects: it is generally available on Lambda, Azure Functions and Google Cloud, and every big compiled package except TensorFlow publishes 3.14 wheels. 3.15 adds a year of support but is still a preview on those platforms, and ONNX Runtime, Ray and PyYAML have no 3.15 wheels yet. It suits containers and Heroku if every dependency has wheels.
When does AWS Lambda stop supporting python3.13?
Lambda deprecates the python3.13 runtime on 30 June 2029, when Amazon Linux 2023 reaches end of life, four months before python.org's date. It blocks creating new python3.13 functions from 31 July 2029 and updating existing ones from 31 August 2029. python3.14 has the same three dates.
Can I still use free-threaded Python 3.13?
The python3.13t build still works, but python.org called it experimental, and the libraries have moved on: NumPy 2.5.0, SciPy 1.18.0, pandas 3.0.4 and PyTorch 2.12.1 all stopped publishing cp313t wheels in June 2026. In 3.14 the free-threaded build is officially supported, and all four publish cp314t wheels.

Also on the calendar

End-of-life dates for the rest of your stack.

Dates checked against endoflife.date (MIT), and the end-of-life date against python.org. How we check datesReport a wrong dateEvery Python version