Quick answers
- Is CVE-2026-106121 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-106121 being exploited in the wild.
- How severe is CVE-2026-106121?
- Medium severity, with a CVSS score of 4.9, published 6 October 2026.
- Which products and versions are affected?
- com.rabbitmq:amqp-client (Maven) <= 5.36.0, ECOSYSTEM:introduced=0,fixed=5.36.1; RabbitMQ Java client library before 5.37.0.
- Is there a fix for CVE-2026-106121?
- Yes. com.rabbitmq:amqp-client (Maven): upgrade to 5.36.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-106121 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-106121?
- Check whether you run com.rabbitmq:amqp-client (Maven) or RabbitMQ Java client library at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- com.rabbitmq:amqp-client (Maven): upgrade to 5.36.1 or later
# set com.rabbitmq:amqp-client to 5.36.1 in your pom.xml or build.gradle
Technical details
The JSONReader.read() method in com.rabbitmq.tools.json fails to properly handle incomplete input: a truncated string causes the parser to append replacement characters until heap exhaustion, while a line comment without a terminating newline causes indefinite CPU consumption. The vulnerable code path is triggered when JSON-RPC message bodies are parsed by DefaultJsonRpcMapper in JsonRpcServer and client replies, with no authentication required since the parser processes untrusted JSON input.
Affected products
- RabbitMQ Java client library before 5.37.0
Identifiers
- CVE-2026-106121
- GHSA-cqgh-8p3p-mx4m
Timeline
- 2026-10-06: disclosed
- 2026-09-21: patched