Release with Go >= 1.27.3 to remediate eMudhra intermediate CA compromise
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Read the release configuration in .promu.yml and .promu-cgo.yml, then check the quay.io/prometheus/golang-builder:1.27-base toolchain and the existing release workflow. Confirm a release binary reports Go 1.27.3 or later, then rebuild and publish container images with updated CA certificates that distrust the named compromised roots.
由索引模型根据 Issue 内容生成。
描述
Summary
Please cut a new node_exporter release built with Go 1.27.3 (or 1.26.10) or later. Those Go versions block the compromised eMudhra intermediates.
Background
On October 19 the Go team shipped Go 1.27.3 and 1.26.10 as an URGENT security release. Those versions block certificates that chain to the eight compromised eMudhra intermediate CAs. The intermediates chain to emSign ECC Root CA – G3. A Go binary is protected only if it is rebuilt with one of the patched toolchains. On Linux, Go uses its own verifier, so updating the host CA store does not fix binaries built with an older Go.
- Go blog: https://go.dev/blog/emudhra-incident
- Background: https://www.keyfactor.com/blog/emudhra-ca-key-compromise-how-to-respond-when-your-ca-loses-trust-overnight/
node_exporter is affected through TLS verification in crypto/x509, for example client certificate verification when --web.config.file is used.
Current state
- The latest release is v1.12.1 (2026-07-14). It was built with Go 1.26 before the fix, so it still trusts the compromised intermediates.
masteris already in good shape:.promu.ymland.promu-cgo.ymluse Go1.27. Thequay.io/prometheus/golang-builder:1.27-baseimage shipsgo1.27.3. A binary built frommasterwith that toolchain reportsgo1.27.3ingo version <binary>, andgovulncheck -mode=binaryfinds no vulnerabilities that the code calls.
So no code changes seem to be needed. Only a release (and refreshed container images) is.
Request
- Cut a release (for example v1.12.2 or v1.13.0) from
masterwith the current Go 1.27.x toolchain (>= 1.27.3). - Rebuild and publish the container images on current base images, so the bundled CA certificates distrust "emSign ECC Root CA - G3" and "Comodo AAA Services root".
Downstream users who bake node_exporter into images are blocked on this. Prometheus v3.15.1 and blackbox_exporter v0.29.1 have already shipped with both changes. The same two [SECURITY] changelog entries would fit here.
Thanks!
- 主要语言
- Go
- 星标
- 13.9k
- 派生
- 2.8k
- 平均合并
- 2 天 10 小时
- 30 天内合并 PR
- 16
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
prometheus/node_exporter 的其他 Issue
-
Darwin diskstats reports operation counts divided by block size as sectors可能已有人在做 @lbarrosby 于 15 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
prometheus/node_exporter#3850 · 2 条评论 ·
维护者通常 1 天内回复
-
node-mixin: Adjust `memory used` Dashboard to use `MemAvailable`可能重新可做 @ojasks 于 52 天前认领,目前没有进行中的 PR。 未关闭
难度 2/5 1-3 小时 新手友好度 75/100
prometheus/node_exporter#3830 · 3 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 84/100
prometheus/node_exporter#3823 · 1 条评论 ·
维护者通常 1 天内回复
-
Fibre Channel collector panics when sysfs statistics counters are missing可能已有人在做 @itjustnathan 于 69 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
prometheus/node_exporter#3817 · 1 个 reaction ·
维护者通常 1 天内回复
-
ZFS collector misparses dataset values that occur in the kstat field prefix可能已有人在做 @vigneshakaviki 于 110 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 76/100
prometheus/node_exporter#3761 ·
维护者通常 1 天内回复
查看 prometheus/node_exporter 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 86/100
txn2/mcp-data-platform#2728 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
blinklabs-io/dingo#6504 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 84/100
SocialGouv/iterion#3413 ·
维护者通常 1 天内回复
-
bug
难度 1/5 1 小时以内 新手友好度 88/100
orion-belt-dev/orion-belt#181 ·
维护者通常 1 天内回复
-
documentation good first issue
难度 2/5 1-3 小时 新手友好度 79/100
kubesmarts/logic-operator#105 ·
维护者通常 1 天内回复