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

Open
#9,844 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

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

Research direction

This is a locked security advisory notice with no code change requested and no contribution path, so there is nothing to implement. A contributor should not pick it up; the actions it lists (updating grpc/grpc to 1.84.1 or google/gax to 1.51.2 in a project's composer.json, and refreshing the OS trust store) belong to downstream users. Done would mean nothing for a newcomer here; questions belong in a new issue.

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 and trust stores are affected

  • Composer package grpc/grpc earlier than 1.84.1 (gRPC transports). The package loads its bundled trust store and does not read the operating system trust store.
  • The operating system's trust store (REST transports).

You can take the following actions to resolve these issues

  • Run composer update grpc/grpc to 1.84.1 or later. 
  • Alternatively, run composer update google/gax to 1.51.2 or later; it requires grpc/grpc 1.84.1 or later and pulls it in.
  • Update the operating system trust store.

Advisory: GHSA-gvrc-7wf9-p7hg (grpc/grpc).

Google Cloud Security Bulletin: GCP-2026-075.

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

Dominant language
PHP
Stars
1.2k
Forks
466
Avg merge
1d 17h
Merged PRs (30d)
40

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-cloud-php

All issues in googleapis/google-cloud-php

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.