Python 3.15.2, 3.14.10, 3.13.18, 3.12.16 and 3.11.18 are out

Here are expedited security releases of Python 3.15, 3.14, 3.13, 3.12 and 3.11.

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.

Security content in all five releases

Additional security content by version

Python 3.13.18, 3.12.16 and 3.11.18

These fixes were already included in Python 3.15.1 and 3.14.9.

Python 3.13.18 and 3.12.16

This fix was already included in Python 3.15.0 and 3.14.9.

  • gh-157579: Fix race condition in the cleanup of tempfile.TemporaryDirectory

For the full details, see the 3.15.2 changelog, 3.14.10 changelog, 3.13.18 changelog, 3.12.16 changelog and 3.11.18 changelog.

Stay safe and upgrade!

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.

Regards from a dark and windy Helsinki,

Your certified release team,
Hugo van Kemenade @hugovk
Thomas Wouters @thomas
Pablo Galindo Salgado @pablogsal
Ned Deily @nad
Steve Dower @steve.dower

22 Likes

Could here be binary or installer for 3.13.18, just like 3.13.17?

2 Likes

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.

7 Likes

The Mostly Official CI Image has been updated, so Python 3.11-3.15 in that image are now fixed.

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.

1 Like

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].


  1. riscv and win-arm64 support starting from 3.14.x ↩︎

  2. glibc 2.17+ (except riscv), macOS 11.0+, windows 10+ ↩︎

5 Likes

Are there other trusted locations if I wanted to get binaries for Windows/macOS for 3.13.18?

I can look into conda-forge

It depends who you trust :slight_smile:

Astral/OpenAI build binaries at Python Build Standalone:

These are used by projects such as uv, Hatch and PDM.

1 Like
1 Like

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.

2 Likes

It’s nice to hear at least someone noticed. :slight_smile:

Aargh, well the space is not intended, I will look into that.

Edit: Oh, that’s the format Sphinx chose.

This is a bug in Sphinx, from code I added in 2023, by copying the PEP and RFC roles which don’t have a hyphen: sphinx-doc/sphinx#11781

Here’s a fix: sphinx-doc/sphinx#14797.

2 Likes

In SUSE we are very proud of our (overly) extensive changelogs, and of course I am stealing from Python ones.

homebrew is also a good source for pre-built python I think

Homebrew Python is not for you.

I use homebrew on my macOS system and cannot recall hitting the issues raised. Is this an out of date blog?

Just to clarify. Regarding emudhra.

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.

1 Like

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!

Here’s one important way these releases make a difference for more recent Pythons: no pip involvement - just plain old urllib.

Given:

mdickinson@MacBook-Pro Desktop % cat bad_urllib.py
import urllib.error
import urllib.request

URL = "https://dv-g3b-emudhra.we-have-a-problem.com/"

try:
    with urllib.request.urlopen(URL) as response:
        print(f"Connected, HTTP {response.status}")
except urllib.error.URLError as e:
    print(f"Failed to connect: {e}")

When I run this under Python 3.15.1 via uv on my (up to date, fully patched) MacBook:

mdickinson@MacBook-Pro Desktop % uv run --python 3.15.1 bad_urllib.py
Connected, HTTP 200

Under Python 3.15.2, we get the desired refusal to connect:

mdickinson@MacBook-Pro Desktop % uv run --python 3.15.2 bad_urllib.py
Failed to connect: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate rejected (_ssl.c:1147)>
2 Likes