Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Netty's netty-codec-http (versions from 4.2.0.Alpha1 before 4.2.13.Final, and 4.1.x before 4.1.133.Final) and netty-codec-http2 (same affected ranges) ignore the maxAllocation limit when HttpContentDecompressor or DelegatingDecompressorFrameListener handles Content-Encoding br, zstd, or snappy. A remote client can send a decompression bomb with one of these encodings and cause unbounded memory allocation, leading to out-of-memory denial of service. Upgrade to netty-codec-http 4.2.13.Final or 4.1.133.Final, and netty-codec-http2 to the same versions.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.5 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0099, the 62nd percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:16 UTC First seen by agentprime
- 31 Oct 2026, 14:16 UTC Confirmed by OSV