CVE-2019-16328: In RPyC 4.1.x through 4.1.1, a remote attacker can dynamically modify object attributes to construct a remote

This week

HIGH 7.5REMOTEUPGRADE

CVE-2019-16328 is a high-severity flaw (CVSS 7.5) affecting rpyc. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

In RPyC 4.1.x through 4.1.1, a remote attacker can dynamically modify object attributes to construct a remote procedure call that executes code for an RPyC service with default configuration settings.

Why this priority

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

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	13.0% (top 4%)
CISA exploited list	No
Weakness	CWE-1321
Published	2019-10-03
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: rpyc project

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

Am I affected?

Timeline

2019-10-03 20:15 UTCPublished CVE record published
2026-06-17 02:22 UTCUpdated Record last modified

rpyc project rpyc UPGRADE

Affected: >= 4.1.0 and <= 4.1.1

Fixed in: newer than 4.1.1

Safe to downgrade to: a release before 4.1.0

1. Check installed version

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

2. UPGRADE to newer than 4.1.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade rpyc

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade rpyc

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 4.1.0 (Debian / Ubuntu)

apt-cache madison rpyc sudo apt install rpyc=<VERSION_BEFORE_4.1.0> sudo apt-mark hold rpyc

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

dnf --showduplicates list rpyc sudo dnf downgrade rpyc-<VERSION_BEFORE_4.1.0> sudo dnf versionlock add rpyc

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.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Metasploit: RPyC 4.1.0 through 4.1.1 Remote Command Execution

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-2019-16328?

rpyc: upgrade to newer than 4.1.1. Exact commands for each OS are on this page.

Is CVE-2019-16328 being exploited?

CVE-2019-16328 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-2019-16328 affect?

CVE-2019-16328 affects rpyc. Severity is high (CVSS 7.5). In RPyC 4.1.x through 4.1.1, a remote attacker can dynamically modify object attributes to construct a remote procedure call that executes code for an RPyC service with default configuration settings.

How urgent is CVE-2019-16328?

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

References

← Back to latest CVEs