Skip to content

chore: update module helm.sh/helm/v3 to v3.18.5 [security] #1437

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Aug 15, 2025

Update Request | Renovate Bot

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
helm.sh/helm/v3 v3.18.4 -> v3.18.5 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2025-55199

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 document.

Credits

Disclosed by Jakub Ciolek at AlphaSense.

CVE-2025-55198

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.


Release Notes

helm/helm (helm.sh/helm/v3)

v3.18.5

Compare Source


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link
Author

renovate bot commented Aug 15, 2025

ℹ Artifact update notice

File name: hack/zstd-dict/go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 14 additional dependencies were updated

Details:

Package Change
github.com/spf13/pflag v1.0.6 -> v1.0.7
golang.org/x/crypto v0.39.0 -> v0.40.0
golang.org/x/sync v0.15.0 -> v0.16.0
golang.org/x/sys v0.33.0 -> v0.34.0
golang.org/x/term v0.32.0 -> v0.33.0
golang.org/x/text v0.26.0 -> v0.27.0
k8s.io/api v0.33.2 -> v0.33.3
k8s.io/apiextensions-apiserver v0.33.2 -> v0.33.3
k8s.io/apimachinery v0.33.2 -> v0.33.3
k8s.io/apiserver v0.33.2 -> v0.33.3
k8s.io/cli-runtime v0.33.2 -> v0.33.3
k8s.io/client-go v0.33.2 -> v0.33.3
k8s.io/component-base v0.33.2 -> v0.33.3
k8s.io/kubectl v0.33.2 -> v0.33.3

@renovate renovate bot force-pushed the renovate/go-helm.sh-helm-v3-vulnerability branch from d1bc2cb to e6cb026 Compare August 15, 2025 11:40
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot force-pushed the renovate/go-helm.sh-helm-v3-vulnerability branch from e6cb026 to e5da26e Compare August 15, 2025 14:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants