NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
HIGH severity

CVE-2019-16328 — rpyc

HIGH

CVE-2019-16328 is a high-severity (CVSS 7.5) CWE-1321 vulnerability in rpyc. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for rpyc — see the affected versions and patch details below.

Duplicate Advisory: Possible remote code execution via a remote procedure call

Also known asGHSA-9ggp-4jpr-7ppjGHSA-pj4g-4488-wmxmPYSEC-2019-118
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
2 known
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
13.0%probability of exploitation in next 30 days
Moderate Risk0.00%
Lower risk than most CVEs96th percentile — riskier than 96% of all scored CVEsHighest risk
0.00%30.3%60.7%91.0%73.0%13.0%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐍rpyc

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Withdrawn: duplicate of GHSA-pj4g-4488-wmxm

Original Description

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.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIrpyc≥ 4.1.0&&< 4.1.24.1.2pip install --upgrade 'rpyc==4.1.2'

Affected Products

1 product · 1 configurations
Application
rpycrpyc_project
≥ 4.1.0 && ≤ 4.1.1
range
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

In RPyC 4.1.x through 4.1.1, a remote attacker can dynamically modify ob…

rpyc.readthedocs.ioNVDAug 2020

Report on github.com

github.comMetasploitMar 2023

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rpyc, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update rpyc to 4.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-16328 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Withdrawn: duplicate of GHSA-pj4g-4488-wmxm ## Original Description 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.
O3 Security · Impact-Aware SCA

Is CVE-2019-16328 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2019-16328: rpyc — Fixed in 4.1.2