Skip to content

build/pkgs: update certifi and pip for the emSign CA security incident - #43034

Merged
vbraun merged 10 commits into
sagemath:developfrom
dimpase:update/certifi-2026.10.19
Oct 22, 2026
Merged

vbraun merged 10 commits into
sagemath:developfrom
dimpase:update/certifi-2026.10.19

Conversation

@dimpase

@dimpase dimpase commented Oct 22, 2026 •

Copy link
Copy Markdown
Member

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.lock security 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:

  • Verified the wheel hashes against PyPI and passed Sage's checksum verification for both packages.
  • Previously installed both wheels offline in a fresh Python 3.14 environment; pip check passed, and both certificate bundles omit the affected G3 root while retaining the unaffected emSign roots.
  • After rebasing, uv lock --check --offline passes against the repository's pyproject.toml.
  • Confirmed all ten conda environments and uv.lock retain the fixed certifi, pip, and uv versions; conda also retains the fixed ca-certificates release.
  • git diff --check passes. Full conda environments and Sage were not rebuilt.

📝 Checklist

  • The title is concise and informative.
  • The description explains in detail what this PR is about.
  • I have linked a relevant issue or discussion.
  • I have created tests covering the changes.
  • I have updated the documentation and checked the documentation preview.

⌛ Dependencies

@dimpase dimpase changed the title build/pkgs: update certifi and pip for the emSign CA security incident Update certifi, pip, uv, and conda certificates for the emSign CA security incident Oct 22, 2026
@github-actions

github-actions Bot commented Oct 22, 2026 •

Copy link
Copy Markdown

Documentation preview for this PR (built with commit a76e4ce; changes) is ready! 🎉
This preview will update shortly after each push to this PR.

@culler culler left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These look like the correct versions and hashes. I don't know how or why coin is involved.

@vincentmacri

Copy link
Copy Markdown
Member

@dimpase Isn't this doing a lot of the same stuff as #43031? Would it make sense to either rebase this on top of #43031 or you can make a PR to merge this into my branch in #43031?

@vincentmacri

vincentmacri commented Oct 22, 2026 •

Copy link
Copy Markdown
Member

Since #43031 is approved and also makes additional package updates to the conda and uv lock files that would probably lead to merge conflicts with this PR, perhaps just drop all the changes outside of build/pkgs from this PR (i.e. revert this to e7efb49)?

@dimpase

dimpase commented Oct 22, 2026

Copy link
Copy Markdown
Member Author

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>
@dimpase dimpase changed the title Update certifi, pip, uv, and conda certificates for the emSign CA security incident build/pkgs: update certifi and pip for the emSign CA security incident Oct 22, 2026
@dimpase
dimpase force-pushed the update/certifi-2026.10.19 branch from 8aaba3b to a76e4ce Compare October 22, 2026 17:17
@dimpase

dimpase commented Oct 22, 2026

Copy link
Copy Markdown
Member Author

@vbraun - this is an urgent security update

@vincentmacri vincentmacri added s: positive review dependencies Pull requests that update a dependency file and removed s: needs review labels Oct 22, 2026
@vbraun
vbraun merged commit 415e5d4 into sagemath:develop Oct 22, 2026
42 of 45 checks passed
@culler

culler commented Oct 26, 2026

Copy link
Copy Markdown
Contributor

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.

@dimpase

dimpase commented Oct 27, 2026

Copy link
Copy Markdown
Member Author

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.

@culler : to be fixed by #43056

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file p: blocker / 1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants