https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 09:05:00 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-10843 bdu:2025-10843 https://cve.radiocsirt.org/vuln/bdu:2025-10843 https://cve.radiocsirt.org/vuln/bit-helm-2025-53547 <p><strong>Affected:</strong> Bitnami: helm</p> <p>Helm is a package manager for Charts for Kubernetes. Prior to 3.18.4, a specially crafted Chart.yaml file along with a specially linked Chart.lock file can lead to local code execution when dependencies are updated. Fields in a Chart.yaml file, that are carried over to a Chart.lock file 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., a bash.rc file or shell script). If the Chart.lock file 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 issue has been resolved in Helm v3.18.4.</p> <p><strong>Affected:</strong> Bitnami: helm</p> <p>Helm is a package manager for Charts for Kubernetes. Prior to 3.18.4, a specially crafted Chart.yaml file along with a specially linked Chart.lock file can lead to local code execution when dependencies are updated. Fields in a Chart.yaml file, that are carried over to a Chart.lock file 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., a bash.rc file or shell script). If the Chart.lock file 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 issue has been resolved in Helm v3.18.4.</p> https://cve.radiocsirt.org/vuln/bit-helm-2025-53547 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0760 certfr-2025-avi-0760 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0760 https://cve.radiocsirt.org/vuln/cleanstart-2026-bt39952 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> CleanStart: consul-k8s-fips</p> <p>Multiple security vulnerabilities affect the consul-k8s-fips package. Moby is an open source container framework developed by Docker Inc. See references for individual vulnerability details.</p> <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> CleanStart: consul-k8s-fips</p> <p>Multiple security vulnerabilities affect the consul-k8s-fips package. Moby is an open source container framework developed by Docker Inc. See references for individual vulnerability details.</p> https://cve.radiocsirt.org/vuln/cleanstart-2026-bt39952 https://cve.radiocsirt.org/vuln/euvd-2026-272795 EUVD-2026-272795 https://cve.radiocsirt.org/vuln/euvd-2026-272795 https://cve.radiocsirt.org/vuln/fkie_cve-2025-53547 <p>Helm is a package manager for Charts for Kubernetes. Prior to 3.18.4, a specially crafted Chart.yaml file along with a specially linked Chart.lock file can lead to local code execution when dependencies are updated. Fields in a Chart.yaml file, that are carried over to a Chart.lock file 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., a bash.rc file or shell script). If the Chart.lock file 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 issue has been resolved in Helm v3.18.4.</p> <p>Helm is a package manager for Charts for Kubernetes. Prior to 3.18.4, a specially crafted Chart.yaml file along with a specially linked Chart.lock file can lead to local code execution when dependencies are updated. Fields in a Chart.yaml file, that are carried over to a Chart.lock file 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., a bash.rc file or shell script). If the Chart.lock file 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 issue has been resolved in Helm v3.18.4.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-53547 https://cve.radiocsirt.org/vuln/ghsa-557j-xg8c-q2mm <p><strong>Affected:</strong> Go: helm.sh/helm/v3</p> <p>A Helm contributor discovered that a specially crafted `Chart.yaml` file along with a specially linked `Chart.lock` file can lead to local code execution when dependencies are updated.</p> <p>### Impact</p> <p>Fields in a `Chart.yaml` file, that are carried over to a `Chart.lock` file 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., a `bash.rc` file or shell script). If the `Chart.lock` file 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.</p> <p>This affects when dependencies are updated. When using the `helm` command this happens when `helm dependency update` is run. `helm dependency build` can write a lock file when one does not exist but this vector requires one to already exist. This affects the Helm SDK when the downloader `Manager` performs an update.</p> <p>### Patches</p> <p>This issue has been resolved in Helm v3.18.4</p> <p>### Workarounds</p> <p>Ensure the `Chart.lock` file in a chart is not a symlink prior to updating dependencies.</p> <p>### For more information</p> <p>Helm&#39;s security policy is spelled out in detail in our [SECURITY](https://github.com/helm/community/blob/master/SECURITY.md) document.</p> <p>### Credits</p> <p>Disclosed by Jakub Ciolek at AlphaSense.</p> <p><strong>Affected:</strong> Go: helm.sh/helm/v3</p> <p>A Helm contributor discovered that a specially crafted `Chart.yaml` file along with a specially linked `Chart.lock` file can lead to local code execution when dependencies are updated.</p> <p>### Impact</p> <p>Fields in a `Chart.yaml` file, that are carried over to a `Chart.lock` file 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., a `bash.rc` file or shell script). If the `Chart.lock` file 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.</p> <p>This affects when dependencies are updated. When using the `helm` command this happens when `helm dependency update` is run. `helm dependency build` can write a lock file when one does not exist but this vector requires one to already exist. This affects the Helm SDK when the downloader `Manager` performs an update.</p> <p>### Patches</p> <p>This issue has been resolved in Helm v3.18.4</p> <p>### Workarounds</p> <p>Ensure the `Chart.lock` file in a chart is not a symlink prior to updating dependencies.</p> <p>### For more information</p> <p>Helm&#39;s security policy is spelled out in detail in our [SECURITY](https://github.com/helm/community/blob/master/SECURITY.md) document.</p> <p>### Credits</p> <p>Disclosed by Jakub Ciolek at AlphaSense.</p> https://cve.radiocsirt.org/vuln/ghsa-557j-xg8c-q2mm https://cve.radiocsirt.org/vuln/msrc_cve-2025-53547 msrc_CVE-2025-53547 https://cve.radiocsirt.org/vuln/msrc_cve-2025-53547 https://cve.radiocsirt.org/vuln/opensuse-su-2025:15331-1 <p>helm-3.18.4-1.1 on GA media</p> <p>helm-3.18.4-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2025:15331-1 https://cve.radiocsirt.org/vuln/rhsa-2025:14821 <p>github.com/golang/glog: Vulnerability when creating log files in github.com/golang/glog helm.sh/helm/v3: Helm Chart Code Execution</p> <p>github.com/golang/glog: Vulnerability when creating log files in github.com/golang/glog helm.sh/helm/v3: Helm Chart Code Execution</p> https://cve.radiocsirt.org/vuln/rhsa-2025:14821 https://cve.radiocsirt.org/vuln/suse-su-2025:20516-1 <p>Security update for helm</p> <p>Security update for helm</p> https://cve.radiocsirt.org/vuln/suse-su-2025:20516-1 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2028 <p>Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Red Hat OpenShift Container Platform ausnutzen, um beliebigen Programmcode auszuführen.</p> <p>Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Red Hat OpenShift Container Platform ausnutzen, um beliebigen Programmcode auszuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2028