CVE-2026-106122 affects the VMware RabbitMQ Java client before 5.36.0. A malformed message property can make reply publication fail and disable consumers. The CVSS score is 7.5 (high).
What is affected
The sources list the affected product as VMware Rabbitmq Java Client, from the vendor VMware. The affected versions are < 5.36.0, meaning all versions before 5.36.0. The library allows Java and JVM-based applications to connect to and interact with RabbitMQ nodes.
The description names two places where the problem appears: the RPC server loop in the library (RpcServer.mainloop()) and consumers written in the style of the project's tutorials. If your applications use the library in either way, they fall within the scope of this advisory.
What the flaw allows
According to the description, the library decodes malformed UTF-8 bytes into replacement characters. When the value is written back out, it can become longer than the AMQP short string limit that the writing code enforces. An attacker who can submit an RPC message with a malformed echoed property can therefore cause the reply to fail with an unchecked exception before the message is acknowledged.
The broker then puts the message back in the queue. The description states that the same message can disable replacement consumers until the queue is purged. The effect is a loss of availability for the affected consumers.
The NVD records a CVSS 3.1 base score of 7.5, which is high severity, with the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. This means the issue can be reached over the network, with low complexity, no privileges and no user interaction. The impact is on availability only. More detail is in the NVD entry for CVE-2026-106122.
Exploitation
The facts used for this advisory do not include a CISA listing of this vulnerability as exploited, and this advisory makes no statement about exploitation. The vulnerability was disclosed on 2026-10-06. Pinet has not analysed or tested the vulnerability; this advisory reports what the public sources say.
What to do
First, find out whether any of your applications or services use the RabbitMQ Java client, including through other libraries that bundle it. Then compare the version in use with the affected range < 5.36.0. The project's pull request and commit describe the change made in the library. The fixed releases are listed in the vendor's published information, and you should update to one of them.
What to do
The sources name no workaround. Identify the applications that use the RabbitMQ Java client in a version in the range < 5.36.0, and update the library to a fixed release listed in the vendor's published information. The project's pull request and the NVD entry give further details.