GPU VulnDB

Database/Container, Kubernetes & orchestration

Helm: index-out-of-range panic rendering charts that contain empty files

CVSS 5.3CVE-2026-63308Container, Kubernetes & orchestrationcurated

Impact

A chart containing a zero-length file makes Helm's Files.Lines helper panic with an index out of range, failing template, install, upgrade, lint and any SDK Engine.Render call. For a GPU fleet this is a deploy-path availability bug, not a node compromise: the chart that ships the device plugin, GPU operator or inference release stops rendering, and a GitOps controller embedding the Helm SDK fails the same way on every reconcile until the chart is fixed. It is deterministic, so a single bad chart blocks rollouts and rollbacks rather than causing intermittent failures. No code execution or data exposure is claimed.

Who can reach it

Anyone who can get a chart into the render path - a chart author, a dependency pulled from a registry, or a user submitting a chart to a CD pipeline. The record requires user interaction (someone must render the chart); no privileges beyond that.

What to do

Upgrade Helm past 4.2.3 to a release containing commit ba6c9a2; replace the client binary and update any service embedding the Helm SDK, then restart that controller. No node drain or reboot is involved. Until then, reject charts containing zero-length files in CI.

References

Related entries

All Container, Kubernetes & orchestration entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.