ghsa-f9f8-9pmf-xv68
Vulnerability from github
Published
2025-08-14 00:05
Modified
2025-08-14 17:15
Severity ?
Summary
Helm May Panic Due To Incorrect YAML Content
Details
A Helm contributor discovered an improper validation of type error when parsing Chart.yaml and index.yaml files that can lead to a panic.
Impact
There are two areas of YAML validation that were impacted. First, when a Chart.yaml
file had a null
maintainer or the child
or parent
of a dependencies import-values
could be parsed as something other than a string, helm lint
would panic. Second, when an index.yaml
had an empty entry in the list of chart versions Helm would panic on interactions with that repository.
Patches
This issue has been resolved in Helm v3.18.5.
Workarounds
Ensure YAML files are formatted as Helm expects prior to processing them with Helm.
References
Helm's security policy is spelled out in detail in our SECURITY document.
Credits
Disclosed by Jakub Ciolek at AlphaSense.
{ "affected": [ { "package": { "ecosystem": "Go", "name": "helm.sh/helm/v3" }, "ranges": [ { "events": [ { "introduced": "0" }, { "fixed": "3.18.5" } ], "type": "ECOSYSTEM" } ] } ], "aliases": [ "CVE-2025-55198" ], "database_specific": { "cwe_ids": [ "CWE-908" ], "github_reviewed": true, "github_reviewed_at": "2025-08-14T00:05:27Z", "nvd_published_at": "2025-08-14T00:15:26Z", "severity": "MODERATE" }, "details": "A Helm contributor discovered an improper validation of type error when parsing Chart.yaml and index.yaml files that can lead to a panic.\n\n### Impact\n\nThere are two areas of YAML validation that were impacted. First, when a `Chart.yaml` file had a `null` maintainer or the `child` or `parent` of a dependencies `import-values` could be parsed as something other than a string, `helm lint` would panic. Second, when an `index.yaml` had an empty entry in the list of chart versions Helm would panic on interactions with that repository.\n\n### Patches\n\nThis issue has been resolved in Helm v3.18.5.\n\n### Workarounds\n\nEnsure YAML files are formatted as Helm expects prior to processing them with Helm.\n\n### References\n\nHelm\u0027s security policy is spelled out in detail in our [SECURITY](https://github.com/helm/community/blob/master/SECURITY.md) document.\n\n### Credits\n\nDisclosed by Jakub Ciolek at AlphaSense.", "id": "GHSA-f9f8-9pmf-xv68", "modified": "2025-08-14T17:15:20Z", "published": "2025-08-14T00:05:27Z", "references": [ { "type": "WEB", "url": "https://github.com/helm/helm/security/advisories/GHSA-f9f8-9pmf-xv68" }, { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-55198" }, { "type": "WEB", "url": "https://github.com/helm/helm/commit/ec5f59e2db56533d042a124f5bae54dd87b558e6" }, { "type": "PACKAGE", "url": "https://github.com/helm/helm" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ], "summary": "Helm May Panic Due To Incorrect YAML Content" }
Loading...
Loading...
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.