Repository navigation
fix: upgrade certifi to 2026.10.19 and pip to 26.2.2 (eMudhra CA removal) - #4
Open
vgulati-apphelix wants to merge 1 commit into
Open
vgulati-apphelix wants to merge 1 commit into
vgulati-apphelix wants to merge 1 commit into
Conversation
…val) The emSign root CA is removed from certifi 2026.10.19 after the eMudhra security incident (GHSA-6q48-6c7w-9gw2). pip vendors its own certifi, so pip must be upgraded to 26.2.2 as well. pip-tools is bumped to 7.6.2, the first release that works with pip 26.2.x. Ticket: LP-1401 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
🟢 Approval recommended
The dependency pins and compatibility constraint are consistent across all six changed files, with no blocking issues identified.
No open issues 🎉
What changed in this PR
Updates the application’s certificate bundle and Python packaging tools to address the eMudhra/emSign CA incident while maintaining pip-tools compatibility.
Changes:
- Upgrades certifi to
2026.10.19across production, test, and development requirements. - Upgrades pip to
26.2.2and pip-tools to7.6.2. - Adjusts the shared pip cap to
<=26.2.2.
Image rebuild and redeployment remain necessary; upgrading the image’s bundled pip requires the separate Dockerfile change noted in the description.
| File | Description |
|---|---|
| requirements/test.txt | Updates the test certificate bundle. |
| requirements/pip.txt | Pins pip to the patched version. |
| requirements/pip-tools.txt | Pins the compatible pip-tools version. |
| requirements/dev.txt | Aligns certifi and pip-tools development pins. |
| requirements/common_constraints.txt | Updates the pip compatibility cap and comment. |
| requirements.txt | Updates the production certificate bundle. |
Review effort: Balanced
rahulkanneri-2u
approved these changes
Oct 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Security fix for the eMudhra / emSign CA incident (GHSA-6q48-6c7w-9gw2). certifi 2026.10.19 removes the compromised emSign root; pip ships its own certifi, so it needs 26.2.2 too.
certifi→ 2026.10.19pip→ 26.2.2 (pip cap, where present locally, →pip<=26.2.2, matching openedx/edx-lint#578)pip-tools→ 7.6.2 (older versions crash with pip 26.2.x)After merge, rebuild and redeploy the image. Note: the
xqueue.Dockerfilein edx/public-dockerfiles creates its venv withpython -m venvand never upgrades pip, so the image's pip stays old until that Dockerfile is updated (separate change). certifi in the image comes fromrequirements.txtand will be 2026.10.19.Supporting information
Testing
pip.txt→ pip-tools → dev/test requirements installs cleanly,pip checkclean (pip 26.2.2, pip-tools 7.6.2, certifi 2026.10.19)requirements.txt(production) installs with certifi 2026.10.19pytest submission_queueagainst a throwaway MySQL 8.0: 41 passed, 4 skipped🤖 Generated with Claude Code