The sources report that the JSON reader in the VMware RabbitMQ Java client, in versions before 5.37.0, can fail to terminate on truncated input. This can lead to denial of service through memory or CPU exhaustion.
What is affected
The VMware Rabbitmq Java Client is a library that lets Java and JVM-based applications connect to and interact with RabbitMQ nodes. The affected versions are given as < 5.37.0, which means all versions before 5.37.0. The issue is tracked as CVE-2026-106121 and was disclosed on 2026-10-06.
The CVSS 3.1 base score is 7.5, which corresponds to a severity of high. The vector describes an issue that can be reached over the network, with low attack complexity, without privileges and without user interaction. The only impact it records is on availability, rated high. Confidentiality and integrity are not affected according to that vector.
What the flaw allows
According to the description in the sources, the JSON reader in the client library does not stop correctly when its input ends inside a quoted string or inside a line comment. The default JSON-RPC mapper, DefaultJsonRpcMapper, passes JSON-RPC message bodies to this reader. This applies to JsonRpcServer and to client replies.
The sources describe two outcomes. With a truncated string, the parser keeps appending end markers until the heap is exhausted. With a line comment that has no terminating newline, a thread can keep consuming CPU indefinitely. In both cases the result is a denial of service for the affected application.
In practice, the applications at risk are those that use the JSON-RPC support of the client library and process message bodies that an outside party can influence. The facts do not say more about specific deployments.
Exploitation
This advisory does not report any exploitation activity. It describes the flaw only as published in the public sources. The NVD entry and the project's pull request and commit are the places to follow any later changes to the record.
What to do
Check whether your applications depend on the VMware Rabbitmq Java Client and which version they use. Pay particular attention to any code that uses the JSON-RPC server or client features. If the version is before 5.37.0, it is within the affected range.
The project's own sources describe the change that addresses the issue, and the fixed releases are listed there. Plan the update through your normal change process, and use the links in the mitigation section for details.
What to do
Update the library to a fixed release listed by the project. The change is described in the RabbitMQ Java client pull request and the corresponding commit, and the record is also available in the NVD entry for CVE-2026-106121. The sources do not state a workaround, so none is suggested here.