CVE-2020-36282: JMS Client for RabbitMQ 1.x before 1.15.2 and 2.x before 2.2.0 is vulnerable to unsafe deserialization that ca

This week

CRITICAL 9.8REMOTEUPGRADE

CVE-2020-36282 is a critical-severity flaw (CVSS 9.8) affecting jms client. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	2.8% (top 13%)
CISA exploited list	No
Weakness	CWE-502
Published	2021-03-12
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: rabbitmq

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2021-03-12 01:15 UTCPublished CVE record published
2026-06-17 03:15 UTCUpdated Record last modified

rabbitmq jms client UPGRADE

Affected: >= 1.0.0 and < 1.15.2 · >= 2.0.0 and < 2.2.0

Fixed in: 1.15.2, 2.2.0

Safe to downgrade to: a release before 1.0.0

1. Check installed version

apt-cache policy jms-client || rpm -q jms-client || jms-client --version

2. UPGRADE to 1.15.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade jms-client

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade jms-client

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 1.0.0 (Debian / Ubuntu)

apt-cache madison jms-client sudo apt install jms-client=<VERSION_BEFORE_1.0.0> sudo apt-mark hold jms-client

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list jms-client sudo dnf downgrade jms-client-<VERSION_BEFORE_1.0.0> sudo dnf versionlock add jms-client

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-36282?

jms client: upgrade to 1.15.2, 2.2.0. Exact commands for each OS are on this page.

Is CVE-2020-36282 being exploited?

CVE-2020-36282 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-36282 affect?

CVE-2020-36282 affects jms client. Severity is critical (CVSS 9.8). 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.

How urgent is CVE-2020-36282?

Priority 61/100. Critical severity; Remotely exploitable, no login, no user action

Software pages

RabbitMQ vulnerabilities

References

← Back to latest CVEs