Is rpc-py safe to use?

Vulert records 2 vulnerabilities for rpc-py in PyPI: 1 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is rpc-py's Vulert package health score?

Vulert scores rpc-py 43/100, which reads as risky. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of rpc-py affected?

Yes. 0.6.0, the version you would install today, has 2 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of rpc-py should I use?

0.4.1 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 rpc-py have?

2 vulnerabilities are recorded for rpc-py in the PyPI ecosystem: 1 critical, 0 high, 0 medium and 0 low, plus 1 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 rpc-py vulnerabilities disclosed?

1 vulnerability was recorded for rpc-py in the last 12 months, and the oldest entry in this database dates to 09 Jul 2022. 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 rpc-py 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 rpc-py for upcoming vulnerabilities?

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

Vulnerability Database · PyPI · Package report

rpc-py: vulnerability history, versions and safety

rpc-py is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 5 releases, from Jul 2022 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

2 vulnerabilities recorded C1 U1

2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →

1 in the last 12 months

Most recent disclosure 29 Jun 2026.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all rpc-py vulnerabilities

Vulert verdict on rpc-py 0.6.0 i

Updated on 23 Oct 2026

Careful: 0.6.0 has 2 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 43/100

Security Some issues to review
Maintenance Slowing
Popularity Little adoption
Community Inactive

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

Current release 0.6.0 — affected i
Vulnerabilities on record 2 over 3 years · 1 in the last year i
Latest disclosure 29 Jun 2026 i
Highest CVSS 9.8 i
With no published fix 2 i
Stars 204 i
OpenSSF scorecard 2/10 i
Last release 54 months ago i
Licence Apache-2.0 i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for rpc-py, 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.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
0.6.0	31 Mar 2022	C1 U1	Apache-2.0	No	Details →
0.5.1	18 Feb 2022	C1 U1	Apache-2.0	No	Details →
0.5.0	05 Mar 2021	C1 U1	Apache-2.0	No	Details →
0.4.3	14 Feb 2021	C1 U1	Apache-2.0	No	Details →
0.4.2	11 Feb 2021	C1 U1	Apache-2.0	No	Details →
0.4.1	03 Dec 2020	none	Apache-2.0	—	Details →
0.4.0	17 Oct 2020	none	Apache-2.0	—	Details →
0.3.1	03 Oct 2020	none	Apache-2.0	—	Details →
0.3.0	09 Aug 2020	none	Apache-2.0	—	Details →
0.2.2	20 Jul 2020	none	Apache-2.0	—	Details →
0.2.1	18 Jul 2020	none	Apache-2.0	—	Details →
0.1.1	16 Jul 2020	none	Apache-2.0	—	Details →

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

02 Disclosure history

How often vulnerabilities are recorded

2022 1
2026 1

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

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for rpc-py

Vulnerability	Severity	Fixed version ↓	Disclosed ↓
CVE-2022-35411: Deserialization of Untrusted Data in rpc-py	9.8 critical	No fix published	09 Jul 2022
CVE-2022-35411: rpc-py Remote Code Execution via Untrusted Data Deserialization	9.8 critical	No fix published	29 Jun 2026

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