CVE-2025-55199: Helm Charts with Specific JSON Schema Values Can Cause Memory Exhaustion

Published Aug 13, 2025
·
Updated

A Helm contributor discovered that it was possible to craft a JSON Schema file in a manner which could cause Helm to use all available memory and have an out of memory (OOM) termination. ### Impact A malicious chart can point `$ref` in _values.schema.json_ to a device (e.g. `/dev/*`) or other problem file which could cause Helm to use all available memory and have an out of memory (OOM) termination. ### Patches This issue has been resolved in Helm v3.18.5. ### Workarounds Make sure that all Helm charts that are being loaded into Helm doesn't have any reference of `$ref` pointing to `/dev/zero`. ### References Helm's security policy is spelled out in detail in our [SECURITY](https://github.com/helm/community/blob/master/SECURITY.md) document. ### Credits Disclosed by Jakub Ciolek at AlphaSense.

Affected Software

3 affected componentsFixes available
Helm helm<3.18.5
go/helm.sh/helm/v3<3.18.5
3.18.5
Helm helm<3.18.5

Event History

Aug 13, 2025
CVE Published
via MITRE·11:23 PM
Data Sourced
via MITRE·11:23 PM
DescriptionSeverityWeakness
Aug 14, 2025
Data Sourced
via Red Hat·12:01 AM
DescriptionSeverityAffected Software
Advisory Published
via GitHub·12:01 AM
Data Sourced
via GitHub·12:01 AM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via NVD·12:15 AM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-55199?

CVE-2025-55199 has a high severity rating due to its potential for causing out of memory (OOM) termination.

2

How do I fix CVE-2025-55199?

To fix CVE-2025-55199, upgrade Helm to version 3.18.5 or later.

3

What software is affected by CVE-2025-55199?

CVE-2025-55199 affects Helm versions prior to 3.18.5.

4

What is the impact of CVE-2025-55199 on Kubernetes deployments?

The impact of CVE-2025-55199 can lead to resource exhaustion and application crashes in Kubernetes environments.

5

Is there a workaround for CVE-2025-55199?

While upgrading to Helm 3.18.5 is the primary fix, temporarily limiting memory usage can serve as a workaround.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203