Improper Certificate Validation Affecting kubeflow-centraldashboard package, versions <2.0.0-r8


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.17% (7th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-KUBEFLOWCENTRALDASHBOARD-22107292
  • published1 Nov 2026
  • disclosed29 Oct 2026

Introduced: 29 Oct 2026

NewCVE-2026-118780  (opens in a new tab)
CWE-295  (opens in a new tab)
CWE-471  (opens in a new tab)

How to fix?

Upgrade Chainguard kubeflow-centraldashboard to version 2.0.0-r8 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kubeflow-centraldashboard package and not the kubeflow-centraldashboard package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementation used pki.verifyCertificateChain(), pki.createCaStore(), duplicate subject names to process the relevant input or security decision. node-forge modified the CA store while trying certificates that shared a subject name during pki.verifyCertificateChain(). A failed chain verification could permanently remove trusted CA certificates from the store, causing later valid chains to fail and creating a persistent availability impact for applications that reused the store. This issue is fixed in version 1.4.1.