Skip to content

Require certifi >= 2026.10.19 for eMudhra CA compromise - #157

Merged
JillRegan merged 1 commit into
mainfrom
jill/bump-certifi-emudhra-fix
Oct 21, 2026
Merged

JillRegan merged 1 commit into
mainfrom
jill/bump-certifi-emudhra-fix

Conversation

@JillRegan

Copy link
Copy Markdown
Contributor

✨ Summary

Fixes exposure to the eMudhra intermediate CA compromise (CVE-2026-111943, https://emudhra.we-have-a-problem.com/).

The SDK uses httpx's default verification, which trusts the user's installed certifi. certifi 2026.10.19 removes emSign ECC Root CA - G3 (AAA Certificate Services was already absent) and keeps the unaffected emSign roots.

  • Add certifi = ">=2026.10.19" to pyproject.toml so installing or upgrading the SDK pulls in a fixed certifi.
  • Relock certifi from 2025.8.3 to 2026.10.19 (dev/test only).
  • Re-pin example/Dockerfile to current python:3.14 and install certifi>=2026.10.19.
  • Add pip and docker to Dependabot.

🕵️ Review Notes & ⚠️ Risks

Needs a release (2.1.1) to reach users. Users on 2.1.0 or older stay exposed until they upgrade the SDK or run pip install -U certifi.

@JillRegan
JillRegan merged commit 7e04a03 into main Oct 21, 2026
7 checks passed
@JillRegan
JillRegan deleted the jill/bump-certifi-emudhra-fix branch October 21, 2026 21:34
@github-actions github-actions Bot mentioned this pull request Oct 21, 2026
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants