<?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://127.0.0.1:10001/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-21T00:02:59.096606+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://127.0.0.1:10001" 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://127.0.0.1:10001/vuln/cve-2026-89092</id>
    <title>CVE-2026-89092 — Stack overflow in nscd due to unbounded alloca use</title>
    <updated>2026-11-21T00:02:59.098912+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> The GNU C Library glibc</p>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>Finally, a crash in nscd may result in performance degradation when 
resolving names, but it does not result in a denial of service.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/cve-2026-89092"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/usn-9065-1</id>
    <title>USN-9065-1 — glibc vulnerabilities</title>
    <updated>2026-11-21T00:02:59.098967+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:22.04:LTS: glibc, Ubuntu:24.04:LTS: glibc, Ubuntu:26.10: glibc, Ubuntu:26.04:LTS: glibc</p>
<p>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)</p>
<p>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)</p>
<p>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)</p>
<p>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)</p>
<p>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)</p>
<p>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…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/usn-9065-1"/>
  </entry>
</feed>
