<?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-10T15:42:31.013631+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-5xqw-8hwv-wg92</id>
    <title>GHSA-5xqw-8hwv-wg92 — Helm Allows A Specially Crafted JSON Schema To Cause A Stack Overflow</title>
    <updated>2026-10-10T15:42:31.015987+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 that a specially crafted JSON Schema within a chart can lead to a stack overflow.</p>
<p>### Impact
A JSON Schema file within a chart can be crafted with a deeply nested chain of references, leading to parser recursion that can exceed the stack size limit and trigger a stack overflow.</p>
<p>### Patches
This issue has been resolved in Helm v3.17.3.</p>
<p>### Workarounds
Ensure that the JSON Schema within any charts loaded by Helm does not have a large number of nested references. These JSON Schema files are larger than 10 MiB.</p>
<p>### For more information
Helm's security policy is spelled out in detail in our [SECURITY](https://github.com/helm/community/blob/master/SECURITY.md) document.</p>
<p>### Credits
Disclosed by Jakub Ciolek at AlphaSense.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-5xqw-8hwv-wg92"/>
  </entry>
</feed>
