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

未关闭
#4,062 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
1/5
预计耗时
1 小时以内
新手友好度
10/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
活跃
技术栈
grpc, node.js, typescript
领域
backend, security

调研方向

The issue names the Node.js runtime trust store and the deprecated grpc npm package as affected. Start by checking whether this repository controls either trust store; the issue directs affected applications to upgrade Node.js or migrate to @grpc/grpc-js. Done means following that guidance; the issue is locked, so questions require a new issue.

由索引模型根据 Issue 内容生成。

描述

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

  • The Node.js runtime's built-in root certificate store.
  • The deprecated native grpc npm package, which bundles a root store and will not be updated.

You can take the following actions to resolve these issues

  • Upgrade Node.js to 26.12.1, 24.22.1 or 22.23.4 or later.
  • If your application still uses the deprecated grpc npm package, migrate to @grpc/grpc-js.

Google Cloud Security Bulletin: GCP-2026-075.

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

主要语言
TypeScript
星标
12.3k
派生
2k
平均合并
3 天 10 小时
30 天内合并 PR
9

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

googleapis/google-api-nodejs-client 的其他 Issue

查看 googleapis/google-api-nodejs-client 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。