VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

rpyc: vulnerability history, versions and safety

rpyc is a package in the PyPI ecosystem. Vulert records 6 vulnerabilities for it across 32 releases, from Oct 2019 to Mar 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
6 vulnerabilities recorded H3 U3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all rpyc vulnerabilities

Vulert verdict on rpyc 6.0.2 i

Updated on 23 Oct 2026

Good news: 6.0.2, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 6.

Package health score 70/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Widely used
  • Community Quiet

What to do: Stay on 6.0.2 or newer. This can change: a vulnerability disclosed tomorrow can affect 6.0.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 6.0.2 — unaffected i
  • Vulnerabilities on record 6 over 4 years · 0 in the last year i
  • Latest disclosure 12 Mar 2024 i
  • Highest CVSS 8.5 i
  • With no published fix 0 i
  • Depended on by 325 packages i
  • Stars 1,703 i
  • OpenSSF scorecard 2/10 i
  • Last release 18 months ago i
  • Licence MIT i
  • Similar names rpy2 i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for rpyc, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
6.0.2 18 Apr 2025 none MIT — Details →
6.0.1 25 Sep 2024 none MIT — Details →
6.0.0 23 Feb 2024 none MIT — Details →
5.3.1 22 Feb 2023 H1 U1 MIT Yes Details →
5.3.0 26 Nov 2022 H1 U1 MIT Yes Details →
5.2.3 04 Aug 2022 H1 U1 MIT Yes Details →
5.2.2 04 Aug 2022 H1 U1 MIT Yes Details →
5.2.1 31 Jul 2022 H1 U1 MIT Yes Details →
5.1.0 26 Feb 2022 H1 U1 MIT Yes Details →
5.0.1 11 Jan 2021 H1 U1 MIT Yes Details →
5.0.0 26 Dec 2020 H1 U1 MIT Yes Details →
4.1.5 25 Apr 2020 H1 U1 MIT Yes Details →
4.1.4 30 Jan 2020 H1 U1 MIT Yes Details →
4.1.3 26 Jan 2020 H1 U1 MIT Yes Details →
4.1.2 03 Oct 2019 H1 U1 MIT Yes Details →
4.1.1 27 Jul 2019 H2 U3 MIT Yes Details →
4.1.0 25 May 2019 H3 U3 MIT Yes Details →
4.0.2 04 Aug 2018 H1 U1 MIT Yes Details →
4.0.1 12 Jun 2018 H1 U1 MIT Yes Details →
4.0.0 11 Jun 2018 H1 U1 MIT Yes Details →
3.4.4 07 Aug 2017 U1 MIT Yes Details →
3.4.3 26 Jul 2017 U1 MIT Yes Details →
3.4.2 14 Jun 2017 U1 MIT Yes Details →
3.4.1 09 Jun 2017 U1 MIT Yes Details →
3.4.0 29 May 2017 U1 MIT Yes Details →
3.3.0 26 Jun 2014 U1 MIT Yes Details →
3.2.3 02 Dec 2012 U1 MIT Yes Details →
3.2.2 31 May 2012 U1 MIT Yes Details →
3.2.1 04 Mar 2012 U1 MIT Yes Details →
3.2.0 30 Sep 2011 U1 MIT Yes Details →
3.2.0.win32 — U1 — Yes Details →
3.2.1.win32 — U1 — Yes Details →
3.2.2.win32 — U1 — Yes Details →
3.2.3.win32 — U1 — Yes Details →
3.3.0.win32 — U1 — Yes Details →

All 35 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 3
  • 2021 1
  • 2024 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 6 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for rpyc

The 5 most severe of 6 vulnerabilities recorded for this package

Search all 6 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2019-16328: RPyC - Dynamic modification of RPyC service due to missing security check 8.5 high 4.1.1 17 Feb 2021
CVE-2024-27758: RPyC's missing security check results in code execution 8.5 high 6.0.0 06 Mar 2024
CVE-2019-16328: RPyC Remote Code Execution N/A unrated 4.1.2 03 Oct 2019
Remote Code Execution Vulnerability in RPyC N/A high 4.1.2 20 Nov 2019
CVE-2019-16328: RPyC Remote Code Execution N/A unrated 4.1.2 03 Oct 2019

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About rpyc

Is rpyc safe to use?

Vulert records 6 vulnerabilities for rpyc in PyPI: 0 critical, 3 high, 0 medium and 0 low, plus 3 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is rpyc's Vulert package health score?

Vulert scores rpyc 70/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of rpyc affected?

No. 6.0.2, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of rpyc should I use?

6.0.2 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does rpyc have?

6 vulnerabilities are recorded for rpyc in the PyPI ecosystem: 0 critical, 3 high, 0 medium and 0 low, plus 3 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new rpyc vulnerabilities disclosed?

0 vulnerabilities were recorded for rpyc in the last 12 months, and the oldest entry in this database dates to 03 Oct 2019. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of rpyc are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor rpyc for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the rpyc version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.