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.
Loading...
Loading...
This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 73.0%, top 1% 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).
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.
October 3, 2019
November 21, 2024
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| rpyc | 4.1.0, 4.1.1 | 4.1.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.
Working exploit code is in the public domain (1 Metasploit module). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
RPyC 4.1.0 through 4.1.1 Remote Command Execution
Open source ↗See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-16328
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.
CWE-1321