Release with Go >= 1.27.3 to remediate eMudhra intermediate CA compromise

未关闭
#3,875 2 条评论 5 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
docker, go
领域
release

调研方向

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.

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.
  • master is already in good shape: .promu.yml and .promu-cgo.yml use Go 1.27. The quay.io/prometheus/golang-builder:1.27-base image ships go1.27.3. A binary built from master with that toolchain reports go1.27.3 in go version <binary>, and govulncheck -mode=binary finds 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 master with 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 模板
  • 阅读贡献指南

从这里开始

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

prometheus/node_exporter 的其他 Issue

查看 prometheus/node_exporter 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

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