Homepage

Buffer Access with Incorrect Length Value The advisory has been revoked - it doesn't affect any version of package eap7-netty-resolver-dns  (opens in a new tab)

Threat Intelligence

EPSS
0.62% (50th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL9-EAP7NETTYRESOLVERDNS-19948139
  • published19 Sept 2026
  • disclosed12 Jun 2026
Report a new vulnerability Found a mistake?

Introduced: 12 Jun 2026

CVE-2026-44893  (opens in a new tab)
CWE-805  (opens in a new tab)

Amendment

The Red Hat security team deemed this advisory irrelevant for RHEL:9.

NVD Description

Note: Versions mentioned in the description apply only to the upstream eap7-netty-resolver-dns package and not the eap7-netty-resolver-dns package as distributed by RHEL.

Netty is a network application framework for development of protocol servers and clients. In netty-codec-haproxy prior to versions 4.1.135.Final and 4.2.15.Final, when decoding a PP2_TYPE_SSL TLV, HAProxyMessage.readNextTLV() first calls header.retainedSlice(header.readerIndex(), length) and only then reads the 1-byte client field and 4-byte verify field. If the attacker sets the TLV length below 5, the subsequent readByte/readInt throws IndexOutOfBoundsException. HAProxyMessageDecoder only catches HAProxyProtocolException around this call, so the IOOBE propagates and the retained slice on the pooled cumulation buffer is never released. Versions 4.1.135.Final and 4.2.15.Final patch the issue.