CVE-2025-55198: GO-2025-3888 - Helm May Panic Due To Incorrect YAML Content in helm.sh/helm

CVE-2025-55198 · Severity: low · CVSS 3.1 · Published 2025-08-18

Helm May Panic Due To Incorrect YAML Content in helm.sh/helm

Technologies: helm.sh/helm (Go), helm.sh/helm/v3 (Go). Vendors: Go.

Quick answers

Is CVE-2025-55198 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-55198 being exploited in the wild.
How severe is CVE-2025-55198?
Low severity, with a CVSS score of 3.1, published 18 August 2025.
Which products and versions are affected?
helm.sh/helm (Go) SEMVER:introduced=0; helm.sh/helm/v3 (Go) SEMVER:introduced=0,fixed=3.18.5.
Is there a fix for CVE-2025-55198?
Yes. helm.sh/helm/v3 (Go): upgrade to 3.18.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-55198?
Check whether you run helm.sh/helm (Go) or helm.sh/helm/v3 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • helm.sh/helm/v3 (Go): upgrade to 3.18.5 or later
    go get helm.sh/helm/v3@v3.18.5

Affected products

  • helm.sh/helm (Go) SEMVER:introduced=0
  • helm.sh/helm/v3 (Go) SEMVER:introduced=0,fixed=3.18.5

Identifiers

  • CVE-2025-55198
  • GHSA-f9f8-9pmf-xv68
  • GO-2025-3888

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.