Request: release built with Go >= 1.26.11 (verified with govulncheck on the v1.12.1 binary)

Aperta
#3,903 0 commenti 2 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
18/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go

Direzione di ricerca

This is release engineering, not a code fix: the requester wants a published node_exporter built with Go >= 1.26.11, verified with govulncheck in binary mode against the distroless image. Start by locating where the Go toolchain version is pinned in the build configuration, bump it, and reproduce the report's check by running govulncheck v1.9.0 in binary mode on the built binary. Done means a subsequent release tag whose binary no longer shows the listed stdlib CVEs with vulnerable functions present. A maintainer schedules the release, so a newcomer can only assist with the bump and verification.

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

Descrizione

Following up on #3868 with verified details rather than scanner output.

We ran govulncheck v1.9.0 in binary mode (vuln.go.dev, DB updated 2026-11-11) on the node_exporter binary from quay.io/prometheus/node-exporter:v1.12.1-distroless (linux/amd64; the same binary as the v1.12.1 image). The binary is built with go1.26.5. govulncheck finds these Go standard library vulnerabilities with the vulnerable functions present in the binary, all fixed in Go 1.26.6:

  • CVE-2026-33818 / GO-2026-5972 - encoding/asn1.Unmarshal
  • CVE-2026-39821 / GO-2026-5026 - net/http client (Transport.RoundTrip)
  • CVE-2026-56853 / GO-2026-6089 - net/http server (Serve, ListenAndServeTLS)
  • CVE-2026-56859 / GO-2026-6088 - encoding/xml decoding
  • CVE-2026-56862 / GO-2026-6090 - crypto/tls handshake and read/write

It also reports CVE-2026-46600 / GO-2026-5942 at package level only (net is present; the vulnerable LookupCNAME functions were not found).

For completeness: the golang.org/x/crypto/ssh advisories (CVE-2026-56854/56855/78662) are not reachable; the ssh package is not compiled into the binary, so we are not asking about those.

Go 1.26.6 was released on 2026-08-13, after v1.12.1. Later Go patch releases (up to 1.26.11) fix further net/http and crypto issues that govulncheck also finds in this binary. Could you share when the next release is planned, built with Go >= 1.26.11? We cannot upgrade until a release exists and will move to it as soon as it is published. Thank you.

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.