<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 30 Sep 2026 03:32:28 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-6791 — Potential stack-based buffer clash during tilde expansion in wordexp</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-6791</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; The GNU C Library glibc&lt;/p&gt;
&lt;p&gt;When expanding paths that begin with a tilde (~) followed by a username, the internal parse_tilde function extracts the username to determine the user&amp;#39;s home directory.  The implementation allocates memory for this username directly on the stack using the strndupa macro. Because the size of this allocation was determined by the length of the user-supplied input without any bounds checks, passing an excessively long username e.g. thousands of characters, forces the thread to exhaust its stack space. Thus if an application passes untrusted, attacker-controlled input to the wordexp function, an attacker can trigger a stack clash.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; The GNU C Library glibc&lt;/p&gt;
&lt;p&gt;When expanding paths that begin with a tilde (~) followed by a username, the internal parse_tilde function extracts the username to determine the user&amp;#39;s home directory.  The implementation allocates memory for this username directly on the stack using the strndupa macro. Because the size of this allocation was determined by the length of the user-supplied input without any bounds checks, passing an excessively long username e.g. thousands of characters, forces the thread to exhaust its stack space. Thus if an application passes untrusted, attacker-controlled input to the wordexp function, an attacker can trigger a stack clash.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-6791</guid>
    </item>
  </channel>
</rss>
