Integer Overflow or Wraparound Affecting io.netty:netty-codec-stomp package, versions [,4.1.138.Final)[4.2.0.Final,4.2.18.Final)
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
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-JAVA-IONETTY-20158641
- published27 Sept 2026
- disclosed10 Sept 2026
- creditHenry Wynn
Introduced: 10 Sep 2026
NewCVE-2026-93560 (opens in a new tab)How to fix?
Upgrade io.netty:netty-codec-stomp to version 4.1.138.Final, 4.2.18.Final or higher.
Overview
Affected versions of this package are vulnerable to Integer Overflow or Wraparound in StompSubframeDecoder.java, where getContentLength() accepts an unbounded long while alreadyReadChunkSize is an int, and the truncating cast at line 149 wraps a value above Integer.MAX_VALUE to a negative number so the chunk accounting never converges. An attacker can pin the event loop thread in a decode loop that never terminates, blocking every subsequent frame on that connection while accumulating chunks in memory, by sending a STOMP frame with a header of content-length: 2147483648. This requires only the ability to send a STOMP frame to the decoder, with no configuration change needed, since the default setup is affected.