Vulert records 2 vulnerabilities for srp in PyPI: 0 critical, 1 high, 0 medium and 0 low, plus 1 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 srp's Vulert package health score?

Vulert scores srp 74/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 srp affected?

No. 1.0.22, 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 srp should I use?

1.0.22 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 srp have?

2 vulnerabilities are recorded for srp in the PyPI ecosystem: 0 critical, 1 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 srp vulnerabilities disclosed?

0 vulnerabilities were recorded for srp in the last 12 months, and the oldest entry in this database dates to 27 Dec 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 srp 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 srp for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at https://vulert.com/scanner and Vulert keeps checking the srp 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

srp: vulnerability history, versions and safety

srp is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 17 releases, first recorded in Dec 2022. 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 H1 U1

0 with no fix published

Every vulnerability has a patched version to move to.

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all srp vulnerabilities

Vulert verdict on srp 1.0.22 i

Updated on 23 Oct 2026

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

Package health score 74/100

Security No known security issues
Maintenance Maintaining
Popularity Niche
Community Quiet

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

Current release 1.0.22 — unaffected i
Vulnerabilities on record 2 over 1 year · 0 in the last year i
Latest disclosure 27 Dec 2022 i
Highest CVSS 7.5 i
With no published fix 0 i
Depended on by 21 packages i
Stars 127 i
Last release 23 months ago i
Licence MIT 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 srp, 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
1.0.22	01 Nov 2024	none	MIT	—	Details →
1.0.21	08 Jul 2024	none	MIT	—	Details →
1.0.20	30 Oct 2022	none	MIT	—	Details →
1.0.19	31 Mar 2022	none	MIT	—	Details →
1.0.18	21 May 2021	none	MIT	—	Details →
1.0.17	01 Feb 2021	none	MIT	—	Details →
1.0.16	05 Mar 2020	H1 U1	MIT	Yes	Details →
1.0.15	15 Oct 2019	H1 U1	MIT	Yes	Details →
1.0.14	04 May 2018	H1 U1	MIT	Yes	Details →
1.0.13	20 Apr 2018	H1 U1	MIT	Yes	Details →
1.0.12	05 Apr 2018	H1 U1	MIT	Yes	Details →
1.0.11	27 Mar 2018	H1 U1	MIT	Yes	Details →
1.0.10	13 Feb 2018	H1 U1	MIT	Yes	Details →
1.0.9	17 Nov 2017	H1 U1	MIT	Yes	Details →
1.0.8	15 Sep 2017	H1 U1	MIT	Yes	Details →
1.0.7	08 May 2017	H1 U1	MIT	Yes	Details →
1.0.6	27 Jul 2016	H1 U1	MIT	Yes	Details →
1.0.5	01 Oct 2014	H1 U1	MIT	Yes	Details →
1.0.4	31 Aug 2013	H1 U1	non-standard	Yes	Details →
1.0.3	16 Aug 2013	H1 U1	non-standard	Yes	Details →
1.0.0	01 Apr 2011	H1	non-standard	Yes	Details →
1.0.1	—	H1	—	Yes	Details →
1.0.2	—	H1	—	Yes	Details →

All 23 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 2

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

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for srp

Vulnerability	Severity	Fixed version ↓	Disclosed ↓
CVE-2021-4286: cocagne pysrp vulnerable to side channel leaks	7.5 high	1.0.17	27 Dec 2022
CVE-2021-4286: cocagne pysrp Information Exposure Vulnerability	N/A unrated	dba52642f5e95d3da7af1780561213ee6053195f	27 Dec 2022

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