Repository navigation
build/pkgs: update certifi and pip for the emSign CA security incident - #43034
Conversation
Ignore another rule ignore redundant condition Another ty ignore
|
Documentation preview for this PR (built with commit a76e4ce; changes) is ready! 🎉 |
culler
left a comment
There was a problem hiding this comment.
These look like the correct versions and hashes. I don't know how or why coin is involved.
|
OK, I will rebase this one on top of #43031 |
Update certifi to 2026.10.19 and pip to 26.2.2, including wheel checksums. The certifi release removes the affected emSign ECC G3 trust root while retaining unaffected emSign roots. Updating pip is also necessary because it vendors its own certifi bundle. See https://discuss.python.org/t/109576 and GHSA-6q48-6c7w-9gw2. Co-authored-by: Codex <codex@openai.com>
8aaba3b to
a76e4ce
Compare
|
@vbraun - this is an urgent security update |
|
Another package which bundles pip wheels is virtualenv. Sage is using version 21.2.0 of virtualenv which bundles a wheel for pip 26.0.1 in its seed directory. Presumably it will create a venv with a vulnerable pip. Supposedly virtualenv 21.14.12 has pip 26.2.2. And they no longer bundle multiple versions of pip. |
|
Depends on #43031.
Update Sage's certifi spkg from 2026.2.25 to 2026.10.19 and pip from 26.0.1 to 26.2.2, including their wheel checksums, to address the compromised eMudhra/emSign intermediate CAs. The corrected certifi bundle removes the affected emSign ECC G3 root while retaining unaffected emSign roots. pip must also be updated because it vendors its own certifi bundle.
These are the versions recommended in the Python security announcement; see also GHSA-6q48-6c7w-9gw2.
This branch is based on #43031, which supplies the conda environment and
uv.locksecurity updates and disables the optional COIN backend. The additional diff here is limited to the certifi and pip spkg versions and checksums. Installations using system packages still depend on their distribution's security updates.Validation:
pip checkpassed, and both certificate bundles omit the affected G3 root while retaining the unaffected emSign roots.uv lock --check --offlinepasses against the repository'spyproject.toml.uv.lockretain the fixed certifi, pip, and uv versions; conda also retains the fixed ca-certificates release.git diff --checkpasses. Full conda environments and Sage were not rebuilt.📝 Checklist
⌛ Dependencies