<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-15T22:21:43.840459+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/cleanstart-2026-fq08949</id>
    <title>CLEANSTART-2026-FQ08949 — Security fix for GHSA-558v-64gr-wgg4 applied in: elasticsearch 9.4.4-r1</title>
    <updated>2026-11-15T22:21:43.844489+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> CleanStart: elasticsearch</p>
<p>Security vulnerability affects the elasticsearch package. This issue is resolved in later releases. See references for vulnerability details.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cleanstart-2026-fq08949"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/cve-2026-59901</id>
    <title>CVE-2026-59901 — Netty Bzip2Decoder: Infinite Loop in RLE State Machine Leads to Event-Loop Thread Hang</title>
    <updated>2026-11-15T22:21:43.844563+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> netty</p>
<p>Netty is an asynchronous, event-driven network application framework. Prior to versions 4.1.136.Final and 4.2.16.Final, the `Bzip2Decoder` handler in Netty's compression codec pipeline is vulnerable to a denial-of-service attack through a malformed bzip2 stream that permanently captures the event-loop thread in an infinite loop. The vulnerability exists in the run-length encoding (RLE) state machine within [`Bzip2BlockDecompressor.read()`]. This issue has been fixed in versions 4.1.136.Final and 4.2.16.Final.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-59901"/>
  </entry>
</feed>
