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

Ouverte
#3,903 0 commentaires 2 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
18/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
go

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Go
Étoiles
13.9k
Forks
2.8k
Merge moyen
2 j 10 h
PR mergées (30 j)
16

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de prometheus/node_exporter

Toutes les issues de prometheus/node_exporter

Issues similaires

Plus d'issues Go

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.