CLI crash via malformed YAML type handling
Published Aug 13, 2025 · Updated Aug 14, 2025
Input-type validation flaws in Helm before 3.18.5 allow remote attackers to crash the CLI through malformed Chart.yaml or index.yaml files. The affected paths dereference a nil maintainer, assert dependency import-values as strings, or retain a nil chart-version entry instead of rejecting malformed YAML. Exploitation requires a user to lint the crafted chart or interact with the malicious repository, and the bounded result is termination of that Helm process.
Summary
What happened
Input-type validation flaws in Helm before 3.18.5 allow remote attackers to crash the CLI through malformed Chart.yaml or index.yaml files. The affected paths dereference a nil maintainer, assert dependency import-values as strings, or retain a nil chart-version entry instead of rejecting malformed YAML. Exploitation requires a user to lint the crafted chart or interact with the malicious repository, and the bounded result is termination of that Helm process.
The record
- CVE
- CVE-2025-55198
- Published
- Aug 13, 2025
- Updated
- Aug 14, 2025
- Vendor
- The Helm Project
- Product
- Helm
- Classifications
- CWE-1287, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 13, 2025CVE publishedPublication date reported by the CVE source.
- Aug 14, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.18.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo