Malformed UTF-8 in RabbitMQ Java client permanently disables RPC consumers
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- Present
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- None · None · High
- Fix status
- Partial Red Hat: 2 without a fix
Attack profile from CVSS 4.0 · CNA. Fix status from CNA, GitHub and Red Hat. Impact type from CWE-248.
Summary
Versions of the RabbitMQ Java client before 5.36.0 are affected. ValueReader.readShortstr decodes malformed UTF-8 into replacement characters that can grow beyond the AMQP shortstr length limit (CWE-172). An attacker who can submit an RPC message with a malformed echoed property makes reply publication throw an unchecked exception, so the message is requeued and blocks consumers until the queue is purged. A public exploit is linked in the references.
Written with Claude Haiku 5.5 from the sources below · 2026-11-03
Description from the CNA
The RabbitMQ Java client library allows Java and JVM-based applications to connect to and interact with RabbitMQ nodes. Prior to 5.36.0, ValueReader.readShortstr decodes malformed UTF-8 bytes into replacement characters that can re-encode beyond the AMQP shortstr limit enforced by ValueWriter.writeShortstr. An attacker who can submit an RPC message with a malformed echoed property can cause reply publication in RpcServer.mainloop() or tutorial-style consumers to throw an unchecked exception before acknowledgement. The broker requeues the message, allowing the same message to disable replacement consumers until the queue is purged. This issue is fixed in version 5.36.0.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
Upgrade the RabbitMQ Java client and com.rabbitmq:amqp-client to version 5.36.0. Red Hat Fuse 7 has no fix planned, and the Red Hat build of Apache Camel 4 for Quarkus 3 has none available.
Written with Claude Haiku 5.5 from the sources below · 2026-11-03
- Fix · CNA rabbitmq-java-client (rabbitmq) Fixed in 5.36.0
- Fix · CNA amqp-client (com.rabbitmq) Fixed in 5.36.0
- Fix · GHSA-7822-rcf6-97fx com.rabbitmq:amqp-client (Maven) Fixed in 5.36.0 Advisory →
Vendor assessments
Red Hat
Red Hat rating: Moderate. Red Hat's page for this CVE →
| Product | Status | Plan or fix |
|---|---|---|
| Red Hat Fuse 7 | Affected | No fix planned: Out of support scope |
| Red Hat build of Apache Camel 4 for Quarkus 3 | Affected | No fix yet: Fix deferred |
Timeline
- 2026-10-06 Threatist record created from CVE-2026-106122
- 2026-10-07 Alias added: GHSA-7822-rcf6-97fx
- 2026-10-07 Fix available: Maven/com.rabbitmq:[email protected] · GHSA-7822-rcf6-97fx
- 2026-10-07 CVSS score added · GHSA-7822-rcf6-97fx
- 2026-10-07 Weakness changed · GHSA-7822-rcf6-97fx
- 2026-10-07 6 new references · GHSA-7822-rcf6-97fx
- 2026-10-09 CVSS score added · NVD
- 2026-11-03 Affected versions changed · Red Hat
- 2026-11-03 CVSS score added · Red Hat
References
Patch 2
More rabbitmq vulnerabilities
- TI-2026-41154 Improper authentication in rabbitmq-server CVSS 3.1CRITICAL 10.0
- TI-2026-41149 RabbitMQ: UNC SSRF affecting the management UI on Windows CVSS 3.1CRITICAL 10.0
- TI-2026-41158 Resource allocation without limits in rabbitmq-server CVSS 3.1HIGH 7.5
- TI-2026-47695 RabbitMQ: OAuth2 Client Secret Exposed via Unauthenticated JavaScript Endpoint CVSS 4.0HIGH 8.2
- TI-2026-47694 RabbitMQ: JWKS Fetch Ignores HTTP Response Status Code - Signing Key Destruction Causes Authentication DoS CVSS 4.0HIGH 8.2
- TI-2026-45167 RabbitMQ Java client: Unvalidated Class.forName in JSON-RPC ProcedureDescription enables arbitrary class loading CVSS 4.0HIGH 7.5
Sources
- CVE-2026-106122 · CVE Program
- CVE-2026-106122 · NVD
- FIRST EPSS
- GHSA-7822-rcf6-97fx · GitHub Advisory Database · CC BY 4.0
- CVE-2026-106122 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences