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

Aperta
#3,875 2 commenti 5 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
docker, go
Ambito
release

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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!

Lingua principale
Go
Stelle
13.9k
Fork
2.8k
Merge medio
2g 10h
PR unite (30g)
16

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di prometheus/node_exporter

Tutte le issue di prometheus/node_exporter

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.