CVE-2020-12835: An issue was discovered in SmartBear ReadyAPI SoapUI Pro 3.2.5

This week

CRITICAL 9.8REMOTEDOWNGRADE

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

An issue was discovered in SmartBear ReadyAPI SoapUI Pro 3.2.5. Due to unsafe use of an Java RMI based protocol in an unsafe configuration, an attacker can inject malicious serialized objects into the communication, resulting in remote code execution in the context of a client-side Network Licensing Protocol component.

Why this priority

Critical severity
EPSS top 4%: very likely to be exploited
Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	13.3% (top 4%)
CISA exploited list	No
Weakness	CWE-502
Published	2020-05-20
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: smartbear

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

Am I affected?

Timeline

2020-05-20 13:15 UTCPublished CVE record published
2026-06-17 02:52 UTCUpdated Record last modified

smartbear readyapi DOWNGRADE

Affected: 3.2.5

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.2.5

1. Check installed version

apt-cache policy readyapi || rpm -q readyapi || readyapi --version

2. No fixed release: DOWNGRADE to a release before 3.2.5 (Debian / Ubuntu)

apt-cache madison readyapi sudo apt install readyapi=<VERSION_BEFORE_3.2.5> sudo apt-mark hold readyapi

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list readyapi sudo dnf downgrade readyapi-<VERSION_BEFORE_3.2.5> sudo dnf versionlock add readyapi

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-12835?

readyapi: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2020-12835 being exploited?

CVE-2020-12835 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-12835 affect?

CVE-2020-12835 affects readyapi. Severity is critical (CVSS 9.8). An issue was discovered in SmartBear ReadyAPI SoapUI Pro 3.2.5. Due to unsafe use of an Java RMI based protocol in an unsafe configuration, an attacker can inject malicious serialized objects into the communication, resulting in remote code

How urgent is CVE-2020-12835?

Priority 68/100. Critical severity; EPSS top 4%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

Java vulnerabilities

Related CVEs

CVE-2019-12180 HIGH 7.8 UPGRADE UPGRADE An issue was discovered in SmartBear ReadyAPI through 2.8.2 and 3.0.0 and SoapUI through 5.5
CVE-2018-20580 HIGH 8.8 DOWNGRADE The WSDL import functionality in SmartBear ReadyAPI 2.5.0 and 2.6.0 allows remote attackers to execute arbitra

References

← Back to latest CVEs