<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-10T10:10:50.433879+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-v53g-5gjp-272r</id>
    <title>GHSA-v53g-5gjp-272r — Helm dependency management path traversal</title>
    <updated>2026-10-10T10:10:50.435124+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: helm.sh/helm/v3</p>
<p>A Helm contributor discovered a path traversal vulnerability when Helm saves a chart including at download time.</p>
<p>### Impact</p>
<p>When either the Helm client or SDK is used to save a chart whose name within the `Chart.yaml` file includes a relative path change, the chart would be saved outside its expected directory based on the changes in the relative path. The validation and linting did not detect the path changes in the name.</p>
<p>### Patches</p>
<p>This issue has been resolved in Helm v3.14.1.</p>
<p>### Workarounds</p>
<p>Check all charts used by Helm for path changes in their name as found in the `Chart.yaml` file. This includes dependencies.</p>
<p>### Credits</p>
<p>Disclosed by Dominykas Blyžė at Nearform Ltd.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-v53g-5gjp-272r"/>
  </entry>
</feed>
