Helm up to 3.17.2 memory allocation

Summaryinfo

A vulnerability marked as problematic has been reported in Helm up to 3.17.2. This affects an unknown function. The manipulation leads to memory allocation. This vulnerability is documented as CVE-2025-32386. The attack can be initiated remotely. There is not any exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in Helm up to 3.17.2. This issue affects an unknown code. The manipulation with an unknown input leads to a memory allocation vulnerability. Using CWE to declare the problem leads to CWE-789. The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated. Impacted is availability. The summary by CVE is:

Helm is a tool for managing Charts. A chart archive file can be crafted in a manner where it expands to be significantly larger uncompressed than compressed (e.g., >800x difference). When Helm loads this specially crafted chart, memory can be exhausted causing the application to terminate. This issue has been resolved in Helm v3.17.3.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2025-32386 since 04/06/2025. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 237919 (SUSE SLES15 / openSUSE 15 Security Update : helm-mirror (SUSE-SU-2025:01830-1)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 3.17.3 eliminates this vulnerability. Applying the patch d8ca55fc669645c10c0681d49723f4bb8c0b1ce7 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at Tenable (237919). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• Helm

Version

• 3.17.0
• 3.17.1
• 3.17.2

License

• open-source

Website

• Product: https://github.com/helm/helm/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion