Netty prior 4.1.135.Final/4.2.15.Final HAProxyMessage.readNextTLV improper check or handling of exceptional conditions
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 5.00- |
Summary
A vulnerability labeled as problematic has been found in Netty. This vulnerability affects the function HAProxyMessage.readNextTLV. Such manipulation leads to improper check or handling of exceptional conditions.
This vulnerability is traded as CVE-2026-44893. The attack may be launched remotely. There is no exploit available.
The affected component should be upgraded.
Details
A vulnerability, which was classified as problematic, has been found in Netty. Affected by this issue is the function HAProxyMessage.readNextTLV. The manipulation with an unknown input leads to a improper check or handling of exceptional conditions vulnerability. Using CWE to declare the problem leads to CWE-703. The product does not properly anticipate or handle exceptional conditions that rarely occur during normal operation of the product. Impacted is availability. CVE summarizes:
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.
The advisory is shared for download at github.com. This vulnerability is handled as CVE-2026-44893 since 05/07/2026. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. There are known technical details, but no exploit is available.
Upgrading to version 4.1.135.Final or 4.2.15.Final eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-1814). Once again VulDB remains the best source for vulnerability data.
Affected
- Open Source Netty
Product
Name
Website
- Product: https://github.com/netty/netty/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.5
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Improper check or handling of exceptional conditionsCWE: CWE-703
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Netty 4.1.135.Final/4.2.15.Final
Timeline
05/07/2026 CVE reserved06/12/2026 Advisory disclosed
06/12/2026 VulDB entry created
06/13/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-44893 (🔒)
GCVE (CVE): GCVE-0-2026-44893
GCVE (VulDB): GCVE-100-370604
CERT Bund: WID-SEC-2026-1814 - Netty: Mehrere Schwachstellen
Entry
Created: 06/12/2026 17:17Updated: 06/13/2026 00:33
Changes: 06/12/2026 17:17 (61), 06/13/2026 00:33 (7)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.