<?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://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>Fri, 20 Nov 2026 23:39:09 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-89092 — Stack overflow in nscd due to unbounded alloca use</title>
      <link>https://127.0.0.1:10001/vuln/cve-2026-89092</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; The GNU C Library glibc&lt;/p&gt;
&lt;p&gt;The nscd service in the GNU C Library 2.3.4 onwards may crash due to a 
stack overflow when a malicious DNS server returns too large a response 
for a DNS query, resulting in degraded DNS resolution for the system.&lt;/p&gt;
&lt;p&gt;Exploitation of this bug needs a system that has nscd enabled and using 
an untrusted DNS server for name resolution, with the compromised DNS 
server being capable of processing records large enough to result in a 
stack overflow in an nscd thread stack.  During experimentation, bind 9 
was unable to handle large records, but that could change in future or 
with a different name server.  In typical installations, nscd is 
executed in an isolated context as its own user without a shell, due to 
which any compromise of that service is isolated.&lt;/p&gt;
&lt;p&gt;There is a remote possibility of nscd cache corruption if an attacker 
manages to get the stack pointer into a desired point in the heap, 
potentially resulting in other caches in nscd being overwritten with 
corrupt data through the stack overflow, until the buggy code path 
eventually results in a crash.&lt;/p&gt;
&lt;p&gt;Finally, a crash in nscd may result in performance degradation when 
resolving names, but it does not result in a denial of service.&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;The nscd service in the GNU C Library 2.3.4 onwards may crash due to a 
stack overflow when a malicious DNS server returns too large a response 
for a DNS query, resulting in degraded DNS resolution for the system.&lt;/p&gt;
&lt;p&gt;Exploitation of this bug needs a system that has nscd enabled and using 
an untrusted DNS server for name resolution, with the compromised DNS 
server being capable of processing records large enough to result in a 
stack overflow in an nscd thread stack.  During experimentation, bind 9 
was unable to handle large records, but that could change in future or 
with a different name server.  In typical installations, nscd is 
executed in an isolated context as its own user without a shell, due to 
which any compromise of that service is isolated.&lt;/p&gt;
&lt;p&gt;There is a remote possibility of nscd cache corruption if an attacker 
manages to get the stack pointer into a desired point in the heap, 
potentially resulting in other caches in nscd being overwritten with 
corrupt data through the stack overflow, until the buggy code path 
eventually results in a crash.&lt;/p&gt;
&lt;p&gt;Finally, a crash in nscd may result in performance degradation when 
resolving names, but it does not result in a denial of service.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/cve-2026-89092</guid>
    </item>
    <item>
      <title>USN-9065-1 — glibc vulnerabilities</title>
      <link>https://127.0.0.1:10001/vuln/usn-9065-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: glibc, Ubuntu:24.04:LTS: glibc, Ubuntu:26.10: glibc, Ubuntu:26.04:LTS: glibc&lt;/p&gt;
&lt;p&gt;It was discovered that the GNU C Library incorrectly handled the ccs=
option in the fopen function. An attacker could possibly use this issue
to cause GNU C Library to crash or execute arbitrary code.
(CVE-2026-18374)&lt;/p&gt;
&lt;p&gt;It was discovered that the GNU C Library incorrectly handled long domain
names in DNS search lists. An attacker on the local network could
possibly use this issue to cause GNU C Library to crash, resulting in a
denial of service. (CVE-2026-8674)&lt;/p&gt;
&lt;p&gt;It was discovered that the GNU C Library dynamic loader had a
time-of-check to time-of-use race condition when handling the $ORIGIN
path expansion in setuid or setgid programs. A local attacker could
possibly use this issue to execute arbitrary code with elevated
privileges. (CVE-2026-86805)&lt;/p&gt;
&lt;p&gt;It was discovered that the GNU C Library dynamic loader incorrectly
handled $ORIGIN path expansion, leading to a stack-based buffer
overflow. A local attacker could possibly use this issue to cause GNU C
Library to crash, resulting in a denial of service, or obtain sensitive
information. (CVE-2026-95818)&lt;/p&gt;
&lt;p&gt;It was discovered that the GNU C Library nscd service incorrectly
handled large DNS responses. An attacker could possibly use this issue
to cause nscd to crash, resulting in a denial of service.
(CVE-2026-89092)&lt;/p&gt;
&lt;p&gt;It was discovered that the GNU C Library strncasecmp function optimized
for the Power8 architecture incorrectly handled certain inputs. An
attacker could possibly use this issue to cause GNU C Library to crash,
resultin…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: glibc, Ubuntu:24.04:LTS: glibc, Ubuntu:26.10: glibc, Ubuntu:26.04:LTS: glibc&lt;/p&gt;
&lt;p&gt;It was discovered that the GNU C Library incorrectly handled the ccs=
option in the fopen function. An attacker could possibly use this issue
to cause GNU C Library to crash or execute arbitrary code.
(CVE-2026-18374)&lt;/p&gt;
&lt;p&gt;It was discovered that the GNU C Library incorrectly handled long domain
names in DNS search lists. An attacker on the local network could
possibly use this issue to cause GNU C Library to crash, resulting in a
denial of service. (CVE-2026-8674)&lt;/p&gt;
&lt;p&gt;It was discovered that the GNU C Library dynamic loader had a
time-of-check to time-of-use race condition when handling the $ORIGIN
path expansion in setuid or setgid programs. A local attacker could
possibly use this issue to execute arbitrary code with elevated
privileges. (CVE-2026-86805)&lt;/p&gt;
&lt;p&gt;It was discovered that the GNU C Library dynamic loader incorrectly
handled $ORIGIN path expansion, leading to a stack-based buffer
overflow. A local attacker could possibly use this issue to cause GNU C
Library to crash, resulting in a denial of service, or obtain sensitive
information. (CVE-2026-95818)&lt;/p&gt;
&lt;p&gt;It was discovered that the GNU C Library nscd service incorrectly
handled large DNS responses. An attacker could possibly use this issue
to cause nscd to crash, resulting in a denial of service.
(CVE-2026-89092)&lt;/p&gt;
&lt;p&gt;It was discovered that the GNU C Library strncasecmp function optimized
for the Power8 architecture incorrectly handled certain inputs. An
attacker could possibly use this issue to cause GNU C Library to crash,
resultin…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/usn-9065-1</guid>
    </item>
  </channel>
</rss>
