They address the compromised eMudhra intermediate CA keys. These keys are now blocked by the ssl module as a last resort against their use. Normal uses of pip, including to upgrade pip itself, are now safe from attacks based on those compromised keys, even if pip hasn’t been updated yet.
Python 3.15.2 and 3.14.10 come with binary installers.
Python 3.13.18, 3.12.16 and 3.11.18 are source-only security releases.
As always, upgrading is highly recommended to all users of affected versions.
Enjoy the new releases
Thanks to all of the many volunteers who help make Python development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organisation contributions to the Python Software Foundation.
No, sorry, we have to draw the line somewhere. If you want to start a new discussion about extending the bugfix phase that’s fine, but we have the policy for a reason. It may not seem like a lot of work to build them, but I don’t want to start releasing installers that look like, but aren’t, bugfix releases.
If you have critical uses of Python 3.13 on macOS or Windows, you should build them yourselves, get binaries from elsewhere, or upgrade to 3.14 or 3.15.
The image still contains 3.16a1 which is not patched. When 3.16a2 is released on its normal schedule the image builder pipeline will pick it up automatically.
FWIW, conda-forge provides easy access to binaries for all supported python versions including the latest round of patch releases, across quite a wide variety of platforms[1] (linux-{x86_64,aarch64,ppc64le,riscv64}, osx-{x86_64,arm64}, win-{x86_64,arm64}), with or without the GIL, against very conservative minimal system requirements[2].
riscv and win-arm64 support starting from 3.14.x ↩︎
glibc 2.17+ (except riscv), macOS 11.0+, windows 10+ ↩︎
One more on changelogs: I am really glad that you are including CVE IDs into the changelog (THANK YOU!), but just a nit: the official format of CVE IDs is with dash not space. https://www.cve.org/CVERecord?id=CVE-2026-114583 points to CVE-2026-114583 not CVE 2026-114583. As these are often processed (semi-)automatically, it would be lovely if you are strict about the format.
This sounds like this update is mostly for 3.11/3.12 since they ship vulnerable pip.
And this update doesn’t make 3.13+ any more secure, it’s just defense in depth? since they all ship secure pip?
Or is there another concern regarding emudhra I missed?
asking because I’m wondering if there is any urgency to update a Windows python app using the prebuilt version of 3.13.17 (not .18). It uses the requests library to make get requests. It has a small dependency issue on 3.14, otherwise I’d just go to prebuilt latest 3.14. It has certifi 2026-10-23. It’s built using GitHub Actions and setup-python action only supports prebuilt python versions
It doesn’t make new virtualenvs created by the venv module more secure, no.
It does make existing venvs with old pips, other virtualenv creations using old bundled CA certs, and any other use of SSL with old bundled CA certs more secure. That includes the use of pip to upgrade pip or other packages that bundle CA certs. I’m not sure if you consider that “any more secure” but I’m going to say that, yeah, most people would probably consider that a little more secure.
Oh, I previously had the incorrect thought that each venv included the python version used at its creation. Now the homebrew python is not for you article makes sense.
And sorry, I forgot to consider older venv since I already manually fixed all of mine.
Thank you for all your python security work and helping me understand!