Update module helm.sh/helm/v3 to v3.18.5 [SECURITY]#8
Open
renovate[bot] wants to merge 1 commit intomainfrom
Open
Update module helm.sh/helm/v3 to v3.18.5 [SECURITY]#8renovate[bot] wants to merge 1 commit intomainfrom
renovate[bot] wants to merge 1 commit intomainfrom
Conversation
Author
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate
bot
force-pushed
the
renovate/go-helm.sh-helm-v3-vulnerability
branch
from
a3b8677 to
78675f2
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/go-helm.sh-helm-v3-vulnerability
branch
from
78675f2 to
f2ad3e1
Compare
Author
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v3.18.3→v3.18.5GitHub Vulnerability Alerts
CVE-2025-53547
A Helm contributor discovered that a specially crafted
Chart.yamlfile along with a specially linkedChart.lockfile can lead to local code execution when dependencies are updated.Impact
Fields in a
Chart.yamlfile, that are carried over to aChart.lockfile when dependencies are updated and this file is written, can be crafted in a way that can cause execution if that same content were in a file that is executed (e.g., abash.rcfile or shell script). If theChart.lockfile is symlinked to one of these files updating dependencies will write the lock file content to the symlinked file. This can lead to unwanted execution. Helm warns of the symlinked file but did not stop execution due to symlinking.This affects when dependencies are updated. When using the
helmcommand this happens whenhelm dependency updateis run.helm dependency buildcan write a lock file when one does not exist but this vector requires one to already exist. This affects the Helm SDK when the downloaderManagerperforms an update.Patches
This issue has been resolved in Helm v3.18.4
Workarounds
Ensure the
Chart.lockfile in a chart is not a symlink prior to updating dependencies.For more information
Helm's security policy is spelled out in detail in our SECURITY document.
Credits
Disclosed by Jakub Ciolek at AlphaSense.
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
$refin 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
$refpointing 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.yamlfile had anullmaintainer or thechildorparentof a dependenciesimport-valuescould be parsed as something other than a string,helm lintwould panic. Second, when anindex.yamlhad 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: Helm v3.18.5Compare Source
Helm v3.18.5 is a security release. Users are encouraged to upgrade for the best experience.
The community keeps growing, and we'd love to see you there!
Security Advisories
Installation and Upgrading
Download Helm v3.18.5. The common platform binaries are here:
The Quickstart Guide will get you going from there. For upgrade instructions or detailed installation notes, check the install guide. You can also use a script to install on any system with
bash.What's Next
Changelog
7799b48(Matt Farina)dd8502f(Matt Farina)cb8595b(Robert Sirchia)v3.18.4: Helm v3.18.4Compare Source
Helm v3.18.4 is a security release. Users are encouraged to upgrade for the best experience.
The community keeps growing, and we'd love to see you there!
Security Advisories
Installation and Upgrading
Download Helm v3.18.4. The common platform binaries are here:
The Quickstart Guide will get you going from there. For upgrade instructions or detailed installation notes, check the install guide. You can also use a script to install on any system with
bash.What's Next
Changelog
f20a4ad(Matt Farina)563b094(dependabot[bot])00de613(Matt Farina)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 becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.