CVE-2019-16328

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 13.0%, top 4% 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).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this weekWeaponized
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 13%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
64(Track)
EG Risk 64/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation65% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
95.9%
KEV
Not listed

Published

October 3, 2019

Last Modified

November 21, 2024

References (8)

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
rpyc4.1.0, 4.1.14.1.2—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 15× in last 7d / 45× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 01:41 UTCEG score recompute
  2. 2026-07-22 22:21 UTCEG score recompute
  3. 2026-07-22 14:05 UTCEPSS rescore
  4. 2026-07-21 15:22 UTCEPSS rescore
  5. 2026-07-21 15:22 UTCEPSS rescore
  6. 2026-07-20 17:04 UTCEPSS rescore
  7. 2026-07-20 17:04 UTCEPSS rescore
  8. 2026-07-20 04:40 UTCOSV refresh
  9. 2026-07-19 14:28 UTCEPSS rescore
  10. 2026-07-19 14:28 UTCEPSS rescore
  11. 2026-07-19 02:26 UTCEPSS rescore
  12. 2026-07-19 02:26 UTCEPSS rescore
  13. 2026-07-18 10:01 UTCEPSS rescore
  14. 2026-07-16 16:59 UTCEPSS rescore
  15. 2026-07-16 16:59 UTCEPSS rescore
  16. 2026-07-15 16:55 UTCEPSS rescore
  17. 2026-07-15 16:55 UTCEPSS rescore
  18. 2026-07-13 22:27 UTCEPSS rescore
  19. 2026-07-12 05:43 UTCEPSS rescore
  20. 2026-07-12 05:43 UTCEPSS rescore
  21. 2026-07-11 08:24 UTCEPSS rescore
  22. 2026-07-11 08:24 UTCEPSS rescore
  23. 2026-07-09 19:06 UTCEPSS rescore
  24. 2026-07-08 15:11 UTCEPSS rescore
  25. 2026-07-07 13:43 UTCEPSS rescore
Show 55 more
  1. 2026-07-06 16:25 UTCEPSS rescore
  2. 2026-07-06 16:25 UTCEPSS rescore
  3. 2026-07-06 02:20 UTCEPSS rescore
  4. 2026-07-05 02:27 UTCEPSS rescore
  5. 2026-07-04 06:28 UTCEPSS rescore
  6. 2026-07-02 20:05 UTCOSV refresh
  7. 2026-07-01 15:03 UTCEPSS rescore
  8. 2026-07-01 15:03 UTCEPSS rescore
  9. 2026-06-30 23:20 UTCEPSS rescore
  10. 2026-06-29 14:03 UTCEPSS rescore
  11. 2026-06-28 14:04 UTCEPSS rescore
  12. 2026-06-28 04:54 UTCEPSS rescore
  13. 2026-06-28 04:54 UTCEPSS rescore
  14. 2026-06-27 03:06 UTCEPSS rescore
  15. 2026-06-25 13:47 UTCEPSS rescore
  16. 2026-06-25 13:47 UTCEPSS rescore
  17. 2026-06-24 14:03 UTCEPSS rescore
  18. 2026-06-24 14:03 UTCEPSS rescore
  19. 2026-06-23 21:31 UTCEPSS rescore
  20. 2026-06-23 21:30 UTCEPSS rescore
  21. 2026-06-22 14:23 UTCEPSS rescore
  22. 2026-06-21 01:57 UTCEPSS rescore
  23. 2026-06-21 01:57 UTCEPSS rescore
  24. 2026-06-18 17:50 UTCEPSS rescore
  25. 2026-06-17 17:50 UTCEPSS rescore
  26. 2026-06-16 17:50 UTCEPSS rescore
  27. 2026-06-15 17:45 UTCEPSS rescore
  28. 2026-06-14 23:15 UTCEPSS rescore
  29. 2026-06-14 23:15 UTCEPSS rescore
  30. 2026-06-14 17:13 UTCOSV refresh
  31. 2026-06-13 22:58 UTCEPSS rescore
  32. 2026-06-12 23:09 UTCEPSS rescore
  33. 2026-06-11 13:58 UTCEPSS rescore
  34. 2026-06-11 13:58 UTCEPSS rescore
  35. 2026-06-10 22:16 UTCEPSS rescore
  36. 2026-06-10 13:19 UTCEPSS rescore
  37. 2026-06-08 14:15 UTCEPSS rescore
  38. 2026-06-08 14:14 UTCEPSS rescore
  39. 2026-06-07 15:23 UTCEPSS rescore
  40. 2026-06-07 15:22 UTCEPSS rescore
  41. 2026-06-06 13:45 UTCEPSS rescore
  42. 2026-06-06 13:45 UTCEPSS rescore
  43. 2026-06-05 22:45 UTCEPSS rescore
  44. 2026-06-05 22:45 UTCEPSS rescore
  45. 2026-06-05 06:08 UTCEPSS rescore
  46. 2026-06-05 06:08 UTCEPSS rescore
  47. 2026-06-02 20:11 UTCEPSS rescore
  48. 2026-06-01 13:50 UTCEPSS rescore
  49. 2026-06-01 13:50 UTCEPSS rescore
  50. 2026-05-31 00:14 UTCEPSS rescore
  51. 2026-05-31 00:14 UTCEPSS rescore
  52. 2026-05-29 13:42 UTCEPSS rescore
  53. 2026-05-27 13:26 UTCEG score recompute
  54. 2026-05-26 07:17 UTCEPSS rescore
  55. 2026-05-26 07:17 UTCEPSS rescore

Publicly available exploits

(1 reference)

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.

  • Metasploitauxiliary/scanner/http/rpyc_rce✓ verified
    First seen Feb 19, 2023

    RPyC 4.1.0 through 4.1.1 Remote Command Execution

    Open source ↗

Frequently asked(5)

What is CVE-2019-16328?
CVE-2019-16328 is a high vulnerability published on October 3, 2019. 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.
When was CVE-2019-16328 disclosed?
CVE-2019-16328 was first published in the National Vulnerability Database on October 3, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-16328 actively exploited?
CVE-2019-16328 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 95.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-16328?
CVE-2019-16328 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2019-16328?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-16328, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-16328

Explore →

Is Your Infrastructure Affected by CVE-2019-16328?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs