CVE-2026-106121: RabbitMQ Denial of Service Vulnerability
MODERATECVE-2026-106121 is a MODERATE (CVSS 4.9) denial of service vulnerability (CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop')) affecting RabbitMQ libraries in the Maven ecosystem. The issue involves jsonreader in the default json-rpc mapper never terminates on truncated input, causing dos. Remediation is available by upgrading affected packages to version 5.36.1.
CVE-2026-106121 at a Glance
Security Impact
CVSS: 4.9
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
How to Fix CVE-2026-106121
To remediate this vulnerability, upgrade all affected RabbitMQ dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
<dependency>
<groupId>com.rabbitmq</groupId>
<artifactId>amqp-client</artifactId>
<version>5.36.1</version>
</dependency>
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:tree -Dincludes=com.rabbitmq
How to Check if You Are Affected
To determine whether your Java application is affected by CVE-2026-106121, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree -Dincludes=com.rabbitmq
Analyze the terminal output to locate any version of RabbitMQ in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 5.36.1), your application is affected.
Note: The mvn dependency:tree -Dincludes=com.rabbitmq command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop'), where the product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop. In RabbitMQ, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-106121 Affected RabbitMQ Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
com.rabbitmq:amqp-client
|
Maven |
< 5.36.1
|
5.36.1
|
References
Frequently Asked Questions
What is CVE-2026-106121?
Which RabbitMQ versions are affected?
What version fixes CVE-2026-106121?
Is amqp-client affected?
What is the CVSS score of CVE-2026-106121?
What CWE is associated with CVE-2026-106121?
How can I check Maven dependencies for CVE-2026-106121?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-cqgh-8p3p-mx4m",
"modified" : "2026-10-07T20:42:33Z",
"published" : "2026-10-07T20:42:33Z",
"aliases" : [ "CVE-2026-106121" ],
"summary" : "RabbitMQ: JSONReader in the default JSON-RPC mapper never terminates on truncated input, causing DoS",
"details" : "## Summary\n\n`com.rabbitmq.tools.json.JSONReader.read()` never returns when its input ends inside a quoted string or a `//` line comment. Both scanners walk the input with `StringCharacterIterator.next()` but only compare against a delimiter, so once the iterator reaches `CharacterIterator.DONE` (``) they loop forever. The string scanner (`string()`, line 210, `while (c != sep)`) also appends `` to a `StringBuilder` every iteration, so it fills the heap and throws `OutOfMemoryError`, taking down the JVM. The comment scanner (`skipWhiteSpace()`, lines 89-92, `while (c != '\\n')`) pins a thread at 100% CPU with no allocation.\n\nThis is reachable with a single message. `JsonRpcServer` and `JsonRpcClient` fall back to `DefaultJsonRpcMapper` whenever no mapper is passed (`JsonRpcServer.java:84` and `:114`, `JsonRpcClient.java:186`), and that mapper hands the raw message body straight to `JSONReader.read()` (`DefaultJsonRpcMapper.java:42` for the server request, `:52` for the client reply). A caller that can publish to the RPC request queue hangs the server; a malicious or MITM'd JSON-RPC service does the same to a client.\n\n## Proof of concept\n\nAgainst `amqp-client` 5.36.0 from Maven Central:\n\n```java\nimport com.rabbitmq.tools.jsonrpc.DefaultJsonRpcMapper;\n\npublic class Poc {\n public static void main(String[] args) {\n DefaultJsonRpcMapper mapper = new DefaultJsonRpcMapper();\n mapper.parse(\"{\\\"method\\\":\\\"x\", String.class); // unterminated string\n // mapper.parse(\"//\", String.class); // unterminated // comment\n System.out.println(\"unreachable\");\n }\n}\n```\n\n`java -Xmx64m -cp amqp-client-5.36.0.jar:. Poc` throws `OutOfMemoryError: Java heap space` in about 0.1s and never prints. Swapping in the `//` line spins at 100% CPU and never returns. A well-formed body such as `{\"method\":\"x\"}` returns immediately.\n\n## Impact\n\nAvailability. One small, unauthenticated message stops a JSON-RPC endpoint: the unterminated string exhausts the heap, the unterminated comment pins a thread forever. Neither is recoverable per request - `JsonRpcServer.doCall` only catches `ClassCastException`, and an `OutOfMemoryError` affects the whole process.\n\n## Scope and fix\n\nOnly applications using the JSON-RPC-over-AMQP tooling (`com.rabbitmq.tools.jsonrpc`) with the default `DefaultJsonRpcMapper` are affected. `DefaultJsonRpcMapper` and `JSONReader` are deprecated in favour of `JacksonJsonRpcMapper`, but both still ship and remain the default when no mapper is supplied. The fix is to stop both loops at `CharacterIterator.DONE`.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Maven",
"name" : "com.rabbitmq:amqp-client"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "5.36.1"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 5.36.0"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/rabbitmq/rabbitmq-java-client/security/advisories/GHSA-cqgh-8p3p-mx4m"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-106121"
}, {
"type" : "WEB",
"url" : "https://github.com/rabbitmq/rabbitmq-java-client/pull/2100"
}, {
"type" : "WEB",
"url" : "https://github.com/rabbitmq/rabbitmq-java-client/commit/25fad817291feff3195c32620117d295598f8b41"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/rabbitmq/rabbitmq-java-client"
}, {
"type" : "WEB",
"url" : "https://github.com/rabbitmq/rabbitmq-java-client/releases/tag/v5.37.0"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-835" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-10-07T20:42:33Z",
"nvd_published_at" : "2026-10-06T19:17:43Z"
}
}