eMudhra/emSign CA compromise (October 2026): what Cloud SDK Python Libraries developers need to do

Open
#2,852 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
15/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
backend, security

Research direction

The issue is a security notice listing affected dependencies and fixed versions; it does not name a repository file or test. Start by checking the project’s security or release documentation and its dependency guidance. Done means developers can find the affected packages and the stated upgrade versions; the issue is locked, so it gives no path for questions or discussion.

Written by the indexing model from the issue text.

Description

Summary

Eight eMudhra (emSign) intermediate CA certificates have recoverable private keys (Mozilla bug 2083449). Clients whose trust store still contains emSign ECC Root CA - G3, emSign Root TLS CA - G3 or AAA Certificate Services can be impersonated by an on-path attacker.

The following packages are affected

  • certifi earlier than 2026.10.19 (REST transports).
  • httplib2 earlier than 0.32.1, used by google-api-python-client and google-auth-httplib2; its bundled trust store is used when certifi is not installed.
  • grpcio earlier than 1.84.1 (gRPC transports); bundled root store, does not read the operating system trust store.

You can take the following actions to resolve these issues

  • Upgrade certifi to 2026.10.19 or later.
  • Upgrade httplib2 to 0.32.1 or later.
  • Upgrade grpcio to 1.84.1 or later. Patch releases for earlier release lines are being published; see GHSA-2xm2-c8xx-p9vh for the current list of fixed versions.

Advisories:

Google Cloud Security Bulletin: GCP-2026-075.

This issue is locked. Please open a new issue for questions.

Dominant language
Python
Stars
9k
Forks
2.6k
Avg merge
28m
Merged PRs (30d)
4

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from googleapis/google-api-python-client

All issues in googleapis/google-api-python-client

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.