<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T06:49:13.911334+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/cve-2026-56819</id>
    <title>CVE-2026-56819 — Netty: HTTP/2 decompression leaks ByteBuf reference count when the decompressor channel is already closed (Direct memor…</title>
    <updated>2026-09-29T06:49:13.935112+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> netty</p>
<p>Netty is a network application framework for development of protocol servers and clients. In versions 4.2.0.Final through 4.2.15.Final and 4.1.0.Final through 4.1.135.Final, a remote unauthenticated peer can leak one direct `ByteBuf` per HTTP/2 `DATA` frame in applications that enable HTTP/2 content decompression via `DelegatingDecompressorFrameListener`. When a `DATA` frame is processed for a stream whose decompressor has already been closed, `Http2Decompressor.decompress(...)` calls `decompressor.writeInbound(data.retain())` and does not release the retained buffer on the error path, eventually exhausting direct memory and crashing the JVM. This issue is fixed in versions 4.1.136.Final and 4.2.16.Final.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-56819"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-93wv-jw9v-4972</id>
    <title>GHSA-93wv-jw9v-4972 — Netty: HTTP/2 decompression leaks ByteBuf reference count when the decompressor channel is already closed (Direct memor…</title>
    <updated>2026-09-29T06:49:13.935225+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Maven: io.netty:netty-codec-http2</p>
<p>### Summary</p>
<p>A remote, unauthenticated peer can leak one direct `ByteBuf` per HTTP/2 `DATA` frame in
applications that enable HTTP/2 content decompression via `DelegatingDecompressorFrameListener`.
When a `DATA` frame is processed for a stream whose decompressor has already been closed,
`Http2Decompressor.decompress(...)` retains the frame buffer but never releases it on the error
path, so its reference count never returns to zero. Repeating this over a long-lived HTTP/2
connection exhausts direct memory and crashes the JVM with `OutOfMemoryError` — a denial of service.</p>
<p>### Details</p>
<p>In `codec-http2/src/main/java/io/netty/handler/codec/http2/DelegatingDecompressorFrameListener.java`,
`Http2Decompressor.decompress(...)` does:</p>
<p>```java
// around line 433
decompressor.writeInbound(data.retain());
```</p>
<p>The argument `data.retain()` is evaluated **before** `writeInbound(...)` executes, incrementing the
buffer's reference count (`refCnt: 1 -&gt; 2`). The very first statement of
`EmbeddedChannel.writeInbound(...)` is `ensureOpen()` (`EmbeddedChannel.java:360`), which throws
`ClosedChannelException` when the decompressor's internal `EmbeddedChannel` has already been closed.</p>
<p>When that happens:
- the `DATA` payload has been `retain()`ed but never entered the pipeline, so the decoder's
  `finally { release() }` never runs;
- the surrounding `catch (Throwable t)` block in `decompress(...)` (around line 451) does **not**
  release the extra reference;
- the input buffer therefore can never…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-93wv-jw9v-4972"/>
  </entry>
</feed>
