CVE-2019-16328: 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 c
Noroxi assessment
Priority: This week (action score 60/100)
- A ready-made attack module is public (Metasploit); exploiting it takes no special expertise.
- A ready-made attack tool exists and the flaw can be exploited over the network without an account, so priority is at least “This week”.
- Probability of exploitation in the next 30 days: 13% (FIRST EPSS); higher than 96.3% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: python-rpyc (openSUSE:Leap 15.1) 4.1.5-lp151.3.3.1; python-rpyc-test (openSUSE:Leap 15.1) 4.1.5-lp151.3.3.1; python-rpyc (openSUSE:Tumbleweed) 6.0.2-1.5, 6.0.0-1.2.
Don’t wait for the next maintenance window. Upgrade to python-rpyc (openSUSE:Leap 15.1) 4.1.5-lp151.3.3.1; python-rpyc-test (openSUSE:Leap 15.1) 4.1.5-lp151.3.3.1; python-rpyc (openSUSE:Tumbleweed) 6.0.2-1.5, 6.0.0-1.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 3, 2019
- Updated
- Jun 16, 2026
- EPSS
- 13.0% · 96th percentile
- CWE
- CWE-1321
Report tools
Action score
60
This week
Don’t wait for the next maintenance window.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 4 / 30 · 13.0%
- Ready-made attack tool
- 26 / 60 · floor: at least 60
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Weaponized exploit exists
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| rpyc project | rpyc | cpe:2.3:a:rpyc_project:rpyc |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- rpyc project rpyc4.1.0 and later · up to 4.1.1 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| openSUSE:Leap 15.1 | python-rpyc | before 4.1.5-lp151.3.3.1 | 4.1.5-lp151.3.3.1 |
| openSUSE:Leap 15.1 | python-rpyc-test | before 4.1.5-lp151.3.3.1 | 4.1.5-lp151.3.3.1 |
| openSUSE:Tumbleweed | python-rpyc | before 6.0.2-1.5 | 6.0.2-1.5 |
| openSUSE:Tumbleweed | python-rpyc | before 6.0.0-1.2 | 6.0.0-1.2 |
| PyPI | rpyc | from 4.1.0 · before 4.1.2 | 4.1.2 |
| PyPI | rpyc | from 4.1.0 · before 4.1.1 | 4.1.1 |
| SUSE:Package Hub 15 SP1 | python-rpyc | before 4.1.5-bp151.2.3.1 | 4.1.5-bp151.2.3.1 |
| SUSE:Package Hub 15 SP1 | python-rpyc-test | before 4.1.5-bp151.2.3.1 | 4.1.5-bp151.2.3.1 |
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| opensuse:python-rpyc | 4.1.5-lp151.3.3.1 · openSUSE:Leap 15.1 | Package registry (OSV) |
| opensuse:python-rpyc-test | 4.1.5-lp151.3.3.1 · openSUSE:Leap 15.1 | Package registry (OSV) |
| PyPI:rpyc | 4.1.1 | Package registry (OSV) |
| PyPI:rpyc | 4.1.2 | Package registry (OSV) |
| suse:python-rpyc | 4.1.5-bp151.2.3.1 · SUSE:Package Hub 15 SP1 | Package registry (OSV) |
| suse:python-rpyc-test | 4.1.5-bp151.2.3.1 · SUSE:Package Hub 15 SP1 | Package registry (OSV) |
Exploit status
Weaponized
A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.
Evidence
- Metasploit module ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Metasploit module | auxiliary/scanner/http/rpyc_rceRPyC 4.1.0 through 4.1.1 Remote Command Executionauxiliary | 2023-02-19 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Metasploit+1234 d
- TodayNov 2, 2026+2587 d
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-1321 · Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.