<?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 osv_homebrew</title>
    <link>https://127.0.0.1:10001</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>Thu, 19 Nov 2026 19:12:39 +0000</lastBuildDate>
    <item>
      <title>BREW-glibc-CVE-2026-97399</title>
      <link>https://127.0.0.1:10001/vuln/brew-glibc-cve-2026-97399</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: glibc&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: glibc&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/brew-glibc-cve-2026-97399</guid>
      <pubDate>Wed, 18 Nov 2026 06:39:18 +0000</pubDate>
    </item>
    <item>
      <title>BREW-glibc-CVE-2026-95818 — AT_SECURE program buffer overflow via $ORIGIN processing</title>
      <link>https://127.0.0.1:10001/vuln/brew-glibc-cve-2026-95818</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: glibc&lt;/p&gt;
&lt;p&gt;A stack-based buffer overflow in the dynamic loader (ld.so) of the GNU C Library (glibc) versions 2.14 through 2.44 allows a local attacker to crash or corrupt the memory of setuid/setgid (AT_SECURE) programs.&lt;/p&gt;
&lt;p&gt;When such a program&amp;#39;s DT_RPATH or DT_RUNPATH begins with $ORIGIN and is followed by NUL or &amp;#39;/&amp;#39; the loader both reads past the end of the path buffer and writes past the end of a stack-allocated internal buffer. The corrupted loader stack can lead to a loader crash (denial of service) and limited disclosure of process memory.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: glibc&lt;/p&gt;
&lt;p&gt;A stack-based buffer overflow in the dynamic loader (ld.so) of the GNU C Library (glibc) versions 2.14 through 2.44 allows a local attacker to crash or corrupt the memory of setuid/setgid (AT_SECURE) programs.&lt;/p&gt;
&lt;p&gt;When such a program&amp;#39;s DT_RPATH or DT_RUNPATH begins with $ORIGIN and is followed by NUL or &amp;#39;/&amp;#39; the loader both reads past the end of the path buffer and writes past the end of a stack-allocated internal buffer. The corrupted loader stack can lead to a loader crash (denial of service) and limited disclosure of process memory.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/brew-glibc-cve-2026-95818</guid>
      <pubDate>Wed, 18 Nov 2026 06:39:18 +0000</pubDate>
    </item>
    <item>
      <title>BREW-glibc-CVE-2026-89092</title>
      <link>https://127.0.0.1:10001/vuln/brew-glibc-cve-2026-89092</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: glibc&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: glibc&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/brew-glibc-cve-2026-89092</guid>
      <pubDate>Wed, 18 Nov 2026 06:39:18 +0000</pubDate>
    </item>
    <item>
      <title>BREW-glibc-CVE-2026-86805 — AT_SECURE programs may load attacker-controlled code via $ORIGIN</title>
      <link>https://127.0.0.1:10001/vuln/brew-glibc-cve-2026-86805</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: glibc&lt;/p&gt;
&lt;p&gt;A time-of-check to time-of-use (TOCTOU) race condition in the dynamic loader (ld.so) of the GNU C Library (glibc) versions 2.14 through 2.44 allows a local attacker to escalate privileges. When expanding $ORIGIN in DT_RPATH for setuid/setgid (AT_SECURE) programs, glibc validates the lexically normalized search path against the trusted directories but then opens the raw, un-normalized path. On systems where the Linux fs.protected_hardlinks sysctl is disabled, a local attacker who hard-links such a program into an attacker-controlled directory and wins a race to replace an intermediate path component with a symbolic link can direct the loader outside the trusted directory, causing it to load an attacker-controlled shared object and execute arbitrary code with the elevated privileges of the program.&lt;/p&gt;
&lt;p&gt;Exploitation requires an installed setuid or setgid binary whose DT_RPATH uses $ORIGIN followed by &amp;#34;..&amp;#34; traversal that normalizes into a trusted directory, and the ability to hard-link that binary and win the race by swapping a path component for a symbolic link. Major Linux-based OS distributions ship with fs.protected_hardlinks enabled by default and mitigate the vulnerability.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: glibc&lt;/p&gt;
&lt;p&gt;A time-of-check to time-of-use (TOCTOU) race condition in the dynamic loader (ld.so) of the GNU C Library (glibc) versions 2.14 through 2.44 allows a local attacker to escalate privileges. When expanding $ORIGIN in DT_RPATH for setuid/setgid (AT_SECURE) programs, glibc validates the lexically normalized search path against the trusted directories but then opens the raw, un-normalized path. On systems where the Linux fs.protected_hardlinks sysctl is disabled, a local attacker who hard-links such a program into an attacker-controlled directory and wins a race to replace an intermediate path component with a symbolic link can direct the loader outside the trusted directory, causing it to load an attacker-controlled shared object and execute arbitrary code with the elevated privileges of the program.&lt;/p&gt;
&lt;p&gt;Exploitation requires an installed setuid or setgid binary whose DT_RPATH uses $ORIGIN followed by &amp;#34;..&amp;#34; traversal that normalizes into a trusted directory, and the ability to hard-link that binary and win the race by swapping a path component for a symbolic link. Major Linux-based OS distributions ship with fs.protected_hardlinks enabled by default and mitigate the vulnerability.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/brew-glibc-cve-2026-86805</guid>
      <pubDate>Wed, 18 Nov 2026 06:39:18 +0000</pubDate>
    </item>
    <item>
      <title>BREW-glibc-CVE-2026-8674 — Assertion failure in the DNS stub resolver with a long search domain</title>
      <link>https://127.0.0.1:10001/vuln/brew-glibc-cve-2026-8674</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: glibc&lt;/p&gt;
&lt;p&gt;Initializing the DNS stub resolver from an /etc/resolv.conf file, or a LOCALDOMAIN environment variable, whose search list contains a domain of roughly 200 characters or more in the GNU C Library version 2.26 to 2.44 results in an assertion failure which aborts the process.&lt;/p&gt;
&lt;p&gt;The resolver truncates the search list when copying it into the fixed-size _res.defdname buffer, then asserts that the copy is consistent with the full configuration.  The consistency check compared against the wrong size and did not handle a first entry that does not fit, so a correctly truncated list failed the assertion.  Any process that resolves names through the library is affected, including long-running processes that reload /etc/resolv.conf on the next query after it changes.  Search domains are commonly written to /etc/resolv.conf from data received over DHCP or from a VPN server, so an attacker on the local network may be able to trigger this without privileges on the target system, subject to validation by the network configuration software.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: glibc&lt;/p&gt;
&lt;p&gt;Initializing the DNS stub resolver from an /etc/resolv.conf file, or a LOCALDOMAIN environment variable, whose search list contains a domain of roughly 200 characters or more in the GNU C Library version 2.26 to 2.44 results in an assertion failure which aborts the process.&lt;/p&gt;
&lt;p&gt;The resolver truncates the search list when copying it into the fixed-size _res.defdname buffer, then asserts that the copy is consistent with the full configuration.  The consistency check compared against the wrong size and did not handle a first entry that does not fit, so a correctly truncated list failed the assertion.  Any process that resolves names through the library is affected, including long-running processes that reload /etc/resolv.conf on the next query after it changes.  Search domains are commonly written to /etc/resolv.conf from data received over DHCP or from a VPN server, so an attacker on the local network may be able to trigger this without privileges on the target system, subject to validation by the network configuration software.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/brew-glibc-cve-2026-8674</guid>
      <pubDate>Wed, 18 Nov 2026 06:39:18 +0000</pubDate>
    </item>
    <item>
      <title>BREW-glibc-CVE-2026-84243</title>
      <link>https://127.0.0.1:10001/vuln/brew-glibc-cve-2026-84243</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: glibc&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: glibc&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/brew-glibc-cve-2026-84243</guid>
      <pubDate>Wed, 18 Nov 2026 06:39:18 +0000</pubDate>
    </item>
    <item>
      <title>BREW-glibc-CVE-2026-80489 — EUC_JISX0213 decoding may hang on crafted input</title>
      <link>https://127.0.0.1:10001/vuln/brew-glibc-cve-2026-80489</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: glibc&lt;/p&gt;
&lt;p&gt;Converting crafted EUC_JISX0213 input to UCS-4 or the internal wide character encoding, for example with iconv, in the GNU C Library version 2.3 to 2.44 may result in the converter making no progress, causing the calling application to hang.&lt;/p&gt;
&lt;p&gt;Some EUC_JISX0213 sequences decode to two code points.  If the output buffer has room for only the first one, the converter stores the second in the conversion state and returns E2BIG, but it never clears that pending character after emitting it on the next call.  The converter then keeps emitting the pending character without consuming further input, so an application that retries the conversion loops forever. The input must be attacker controlled and the application must convert it with an output buffer small enough to split the two code points. Only the EUC_JISX0213 character set is affected, which is not commonly used.  The related defect in SHIFT_JISX0213 converter is tracked separately as CVE-2026-77117.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: glibc&lt;/p&gt;
&lt;p&gt;Converting crafted EUC_JISX0213 input to UCS-4 or the internal wide character encoding, for example with iconv, in the GNU C Library version 2.3 to 2.44 may result in the converter making no progress, causing the calling application to hang.&lt;/p&gt;
&lt;p&gt;Some EUC_JISX0213 sequences decode to two code points.  If the output buffer has room for only the first one, the converter stores the second in the conversion state and returns E2BIG, but it never clears that pending character after emitting it on the next call.  The converter then keeps emitting the pending character without consuming further input, so an application that retries the conversion loops forever. The input must be attacker controlled and the application must convert it with an output buffer small enough to split the two code points. Only the EUC_JISX0213 character set is affected, which is not commonly used.  The related defect in SHIFT_JISX0213 converter is tracked separately as CVE-2026-77117.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/brew-glibc-cve-2026-80489</guid>
      <pubDate>Wed, 18 Nov 2026 06:39:18 +0000</pubDate>
    </item>
    <item>
      <title>BREW-glibc-CVE-2026-77117 — SHIFT_JISX0213 decoding may hang on crafted input</title>
      <link>https://127.0.0.1:10001/vuln/brew-glibc-cve-2026-77117</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: glibc&lt;/p&gt;
&lt;p&gt;Converting crafted SHIFT_JISX0213 input to UCS-4 or the internal wide character encoding, for example with iconv, in the GNU C Library version 2.3 to 2.44 may result in the converter making no progress, causing the calling application to hang.&lt;/p&gt;
&lt;p&gt;Some SHIFT_JISX0213 sequences decode to two code points.  If the output buffer has room for only the first one, the converter stores the second in the conversion state and returns E2BIG, but it never clears that pending character after emitting it on the next call.  The converter then keeps emitting the pending character without consuming further input, so an application that retries the conversion loops forever. The input must be attacker controlled and the application must convert it with an output buffer small enough to split the two code points. Only the SHIFT_JISX0213 character set is affected, which is not commonly used.  The related defect in the EUC_JISX0213 converter is tracked separately as CVE-2026-80489.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: glibc&lt;/p&gt;
&lt;p&gt;Converting crafted SHIFT_JISX0213 input to UCS-4 or the internal wide character encoding, for example with iconv, in the GNU C Library version 2.3 to 2.44 may result in the converter making no progress, causing the calling application to hang.&lt;/p&gt;
&lt;p&gt;Some SHIFT_JISX0213 sequences decode to two code points.  If the output buffer has room for only the first one, the converter stores the second in the conversion state and returns E2BIG, but it never clears that pending character after emitting it on the next call.  The converter then keeps emitting the pending character without consuming further input, so an application that retries the conversion loops forever. The input must be attacker controlled and the application must convert it with an output buffer small enough to split the two code points. Only the SHIFT_JISX0213 character set is affected, which is not commonly used.  The related defect in the EUC_JISX0213 converter is tracked separately as CVE-2026-80489.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/brew-glibc-cve-2026-77117</guid>
      <pubDate>Wed, 18 Nov 2026 06:39:18 +0000</pubDate>
    </item>
    <item>
      <title>BREW-glibc-CVE-2026-6791 — Potential stack-based buffer clash during tilde expansion in wordexp</title>
      <link>https://127.0.0.1:10001/vuln/brew-glibc-cve-2026-6791</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: 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; Homebrew: 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://127.0.0.1:10001/vuln/brew-glibc-cve-2026-6791</guid>
      <pubDate>Wed, 18 Nov 2026 06:39:18 +0000</pubDate>
    </item>
    <item>
      <title>BREW-glibc-CVE-2026-6368 — wordexp with WRDE_APPEND can return or use invalid memory</title>
      <link>https://127.0.0.1:10001/vuln/brew-glibc-cve-2026-6368</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: glibc&lt;/p&gt;
&lt;p&gt;Calling wordexp with WRDE_APPEND in the GNU C Library version 2.0 to version 2.43 can cause the interface to return invalid memory in the we_wordv member, which on subsequent calls to wordfree may abort the process.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: glibc&lt;/p&gt;
&lt;p&gt;Calling wordexp with WRDE_APPEND in the GNU C Library version 2.0 to version 2.43 can cause the interface to return invalid memory in the we_wordv member, which on subsequent calls to wordfree may abort the process.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/brew-glibc-cve-2026-6368</guid>
      <pubDate>Wed, 18 Nov 2026 06:39:18 +0000</pubDate>
    </item>
  </channel>
</rss>
