[🐛 Bug]: Chart release / rebuild needed: node-chromium ships Chromium with unpatched CVEs

Abierto
#3,247 2 comentarios 0 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
45/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
debian, docker, helm

Línea de trabajo

Start by tracing how the selenium-grid chart records appVersion and how node-chromium images are rebuilt and released. Compare chart 0.59.1 and image 4.48.0-20260905 with application 4.49.0-20260909 and current Debian sid Chromium; done means a chart release exposes the newer application and the rebuilt image addresses the reported Chromium CVEs.

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

Descripción

needs-triaging
What happened?
  1. No chart release carries application 4.49.0-20260909.
    Application 4.49.0-20260909 was published 2026-09-17, but selenium-grid chart 0.59.1 was cut 2026-09-05 and still pins appVersion: 4.48.0-20260905. trunk also still reports 0.59.1 / 4.48.0-20260905. Chart and application have shipped same-day for six consecutive releases (0.55.0/4.44.0 → 0.59.1/4.48.0), so this looks like an unintentional gap. Consumers deploying by chart version cannot reach 4.49.0 without pinning image tags ahead of the chart.

  2. node-chromium is behind Debian on Chromium.
    node-chromium:4.49.0-20260909 carries chromium-l10n 152.0.7977.82. Debian sid now packages chromium 154.0.8037.57-1 for both amd64 and arm64. A rebuild against current sid would pick up 154.x and clear a large set of Critical/High CVEs — 62 on our scan alone require ≥ 153.0.8010.36, including CISA KEV CVE-2026-87491.

Is a rebuild on the current cadence expected?

Command used to start Selenium Grid with Docker (or Kubernetes)
not relevant
Relevant log output
not relevant
Operating System

arm64

Docker Selenium version (image tag)

4.48.0-20260905

Selenium Grid chart version (chart version)

0.59.1

Lenguaje dominante
Go
Estrellas
8.7k
Forks
2.5k
Merge medio
2 d 7 h
PR fusionados (30 d)
28

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 SeleniumHQ/docker-selenium

Todos los issues de SeleniumHQ/docker-selenium

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.