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

Abierto
#3,903 0 comentarios 2 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
18/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Go
Estrellas
13.9k
Forks
2.8k
Merge medio
2 d 10 h
PR fusionados (30 d)
16

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de prometheus/node_exporter

Todos los issues de prometheus/node_exporter

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.