[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <eb4db79e-0510-45dc-a023-a64853b14213@oracle.com>
Date: Thu, 22 Oct 2026 13:43:08 -0700
From: Alan Coopersmith <alan.coopersmith@...cle.com>
To: oss-security@...ts.openwall.com
Subject: Information for Python users regarding eMudhra /
emSign CA certificate security incident
https://discuss.python.org/t/information-for-python-users-regarding-emudhra-emsign-ca-certificate-security-incident/109576
has this statement from Seth Michael Larson:
> A security incident affecting eMudhra intermediate certificates has
> required removing the emSign root CA certificate from CA bundles such
> as “certifi”. It’s important to immediately upgrade the software
> packages below to at least the versions specified and rebuild
> container images with layer caching disabled to fetch the latest
> system certificates. Failure to do so could result in
> monster-in-the-middle (MITM) attacks against TLS clients, including
> python.org and pypi.org .
>
> certifi 2026.10.19 (1)
> pip 26.2.2
> uv 0.13.4
> sigstore 4.5.1
> conda 26.9.4
> pixi 0.82.1
>
> (1): Advisory mentions 2026.10.18, but 2026.10.19 is recommended for
> compatibility with unaffected emSign root certificates.
>
> For all existing virtual environments on your system, please upgrade
> pip and uv to the latest versions. You can update pip securely by
> running the following command and then use this secure pip
> installation to upgrade certifi and uv:
>
> python -m pip install "pip @ https://files.pythonhosted.org/packages/3f/06/3e4420302363fbb71be3c7f35ce042f54bfca330e3e66b3a2e3c4cca579f/pip-26.2.2-py3-none-any.whl#sha256=fd7f4dfa8190e014013b9f08f3e973f4e4c26ffd179a204895533a7254813a70"
>
> Note that the certifi CA bundle is included in the macOS installation
> of Python from python.org. To upgrade certificates for this
> installation and pip itself, run the command below like so:
>
> /Library/Frameworks/Python.framework/Versions/3.15/bin/python3.15 -m pip install "pip @ https://files.pythonhosted.org/packages/3f/06/3e4420302363fbb71be3c7f35ce042f54bfca330e3e66b3a2e3c4cca579f/pip-26.2.2-py3-none-any.whl#sha256=fd7f4dfa8190e014013b9f08f3e973f4e4c26ffd179a204895533a7254813a70"
> /Library/Frameworks/Python.framework/Versions/3.15/bin/python3.15 -m pip install --upgrade certifi
> /Library/Frameworks/PythonT.framework/Versions/3.15/bin/python3.15t -m pip install "pip @ https://files.pythonhosted.org/packages/3f/06/3e4420302363fbb71be3c7f35ce042f54bfca330e3e66b3a2e3c4cca579f/pip-26.2.2-py3-none-any.whl#sha256=fd7f4dfa8190e014013b9f08f3e973f4e4c26ffd179a204895533a7254813a70"
>
> This topic will be updated as more information is made available.
A comment on it from Christian Helms adds:
> Just to stress one point: users must update pip to >= 26.2.2.
>
> pip always loads the CA certificates from its vendored certifi in
> addition to the system trust store, and there is no supported way to
> disable this. REQUESTS_CA_BUNDLE / --cert only add CAs; truststore is
> used “in addition to certifi” by design. As a result, any pip < 26.2.2
> will keep trusting the compromised intermediate CAs regardless of the
> system trust store, so distrusting them at the OS level is not enough.
>
> uv users can block the bad certs in their system trust store and
> UV_SYSTEM_CERTS=true. That does not work with pip. Updating pip is the
> only reliable fix. See Switch to using truststore only by default
> (currently mixed certifi + truststore) · Issue #14374 · pypa/pip ·
> GitHub
>
> PS: The ‘security incident’ is a bad private key. An elliptic key with
> private key value d=4 is not secure… All 8 eMudhra CAs had private
> keys with d < 256.
Powered by blists - more mailing lists
Please check out the
Open Source Software Security Wiki, which is counterpart to this
mailing list.
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
