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

Aperta
#3,247 2 commenti 0 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
45/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
debian, docker, helm

Direzione di ricerca

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.

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

Descrizione

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

Lingua principale
Go
Stelle
8.7k
Fork
2.5k
Merge medio
2g 7h
PR unite (30g)
28

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

Tutte le issue di SeleniumHQ/docker-selenium

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.