Encoding Error Affecting com.rabbitmq:amqp-client package, versions [,5.36.0)
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-COMRABBITMQ-20562043
- published7 Oct 2026
- disclosed6 Oct 2026
- creditba-am
Introduced: 6 Oct 2026
NewCVE-2026-106122 (opens in a new tab)How to fix?
Upgrade com.rabbitmq:amqp-client to version 5.36.0 or higher.
Overview
Affected versions of this package are vulnerable to Encoding Error in ValueWriter.writeShortstr in com.rabbitmq.client.impl, reached because ValueReader.readShortstr substitutes U+FFFD for malformed UTF-8 bytes on decode, so each bad byte re-encodes to three and a 255 byte shortstr property grows to as much as 765 bytes, past the shortstr limit. A user with permission to publish to the RPC queue can permanently disable the consumer by sending one message carrying malformed UTF-8 in a shortstr property, which raises IllegalArgumentException out of RpcServer.mainloop(). The message is never acknowledged, so it requeues and disables in turn every consumer that takes it, including those re-established through RecordedConsumer.recover(), and service is not restored until an operator purges the queue.