JMS Client for RabbitMQ 1.x before 1.15.2 and 2.x before 2.2.0 is vulnerable to unsafe deserialization that can result in code execution via crafted StreamMessage data.
Loading...
Loading...
This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 1.7%, top 17% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
JMS Client for RabbitMQ 1.x before 1.15.2 and 2.x before 2.2.0 is vulnerable to unsafe deserialization that can result in code execution via crafted StreamMessage data.
March 12, 2021
November 21, 2024
Patch available: rabbitmq/rabbitmq-jms-client v2.2.0
https://github.com/rabbitmq/rabbitmq-jms-client/releases/tag/v2.2.0Patch available: rabbitmq/rabbitmq-jms-client v1.15.2
https://github.com/rabbitmq/rabbitmq-jms-client/releases/tag/v1.15.2| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| com.rabbitmq.jms:rabbitmq-jms | 1.10.0 ... 1.9.0 (16 versions) | 1.15.2 | — |
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.
See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-36282
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.
CWE-502