cve.bz

CVE-2026-106122 vmware rabbitmq java client: Improper Encoding or Decoding of Data

6.0 mediumExploit referenceEPSS 0.5%Fix available

Medium (6.0) in vmware rabbitmq java client. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in com.rabbitmq:amqp-client 5.36.0.

On this page
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.

Severity

CVSS 4.0

6.0 medium
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 43rd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-10-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-172 Improper Encoding or Decoding of Data
CWE-248 Uncaught Exception
OWASP Top 10
A10:2025 Mishandling of Exceptional Conditions
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-106122 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-106122?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-106122?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-106122 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-106122

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-106122](https://cve.bz/cve/badge/CVE-2026-106122.svg)](https://cve.bz/cve/CVE-2026-106122)

HTML:

<a href="https://cve.bz/cve/CVE-2026-106122"><img src="https://cve.bz/cve/badge/CVE-2026-106122.svg" alt="CVE-2026-106122"></a>

Affected

Versions

From the NVD's CPE matches.

ProductAffected
vmware:rabbitmq_java_clientbefore 5.36.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-7822-rcf6-97fxMavencom.rabbitmq:amqp-client<5.36.05.36.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13rabbitmq-java-clientno fix listedDEBIAN-CVE-2026-106122
Ubuntu18.04:LTS, 20.04:LTS, 22.04:LTS and 3 morerabbitmq-java-clientno fix listedUBUNTU-CVE-2026-106122

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Attack patterns (CAPEC)

  • CAPEC-3 Using Leading 'Ghost' Character Sequences to Bypass Input Filters Likelihood: Medium · Severity: Medium
  • CAPEC-52 Embedding NULL Bytes Likelihood: High · Severity: High
  • CAPEC-53 Postfix, Null Terminate, and Backslash Likelihood: High · Severity: High
  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-71 Using Unicode Encoding to Bypass Validation Logic Likelihood: Medium · Severity: High
  • CAPEC-72 URL Encoding Likelihood: High · Severity: High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-80 Using UTF-8 Encoding to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-120 Double Encoding Likelihood: Low · Severity: Medium
  • CAPEC-267 Leverage Alternate Encoding Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON