Service interruption via oversized LZ4 frame allocation
Published May 13, 2026 · Updated May 13, 2026
Resource exhaustion in Netty 4.1.132.Final and earlier and 4.2.0.Alpha1 through 4.2.12.Final allows remote attackers to interrupt service. Lz4FrameDecoder trusts decompressedLength from each frame header and allocates a ByteBuf of that size, up to 32 MB, after receiving as little as 22 bytes. The application must place this decoder on a peer-reachable channel; repeated crafted frames consume memory without granting data access or modification.
Summary
What happened
Resource exhaustion in Netty 4.1.132.Final and earlier and 4.2.0.Alpha1 through 4.2.12.Final allows remote attackers to interrupt service. Lz4FrameDecoder trusts decompressedLength from each frame header and allocates a ByteBuf of that size, up to 32 MB, after receiving as little as 22 bytes. The application must place this decoder on a peer-reachable channel; repeated crafted frames consume memory without granting data access or modification.
The record
- CVE
- CVE-2026-42583
- Published
- May 13, 2026
- Updated
- May 13, 2026
- Vendor
- The Netty Project
- Product
- netty-codec-compression
- Classifications
- CWE-400, CWE-770, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 13, 2026CVE publishedPublication date reported by the CVE source.
- May 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 4.2.13.Final
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream 22-byte LZ4 allocation proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo