VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

rply: vulnerability history, versions and safety

rply is a package in the PyPI ecosystem. Vulert records 5 vulnerabilities for it across 13 releases, from Jan 2014 to May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded M1 L1 U3
i
1 with no fix published

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

See the unfixed vulnerabilities →
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 rply vulnerabilities

Vulert verdict on rply 0.7.8 i

Updated on 23 Oct 2026

Careful: 0.7.8 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security No known security issues
  • Maintenance Slowing
  • Popularity Widely used
  • Community Not enough data

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.7.8 — affected i
  • Vulnerabilities on record 5 over 8 years · 0 in the last year i
  • Latest disclosure 17 May 2022 i
  • Highest CVSS 5.5 i
  • With no published fix 1 i
  • Depended on by 134 packages i
  • Last release 68 months ago i
  • Licence BSD-3-Clause i
  • Similar names ply 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 rply, 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
0.7.8 27 Jan 2021 U1 BSD-3-Clause No Details →
0.7.7 22 Jan 2019 U1 BSD-3-Clause No Details →
0.7.6 26 May 2018 U1 — No Details →
0.7.5 12 Jul 2017 U1 — No Details →
0.7.4 01 Sep 2015 U1 — No Details →
0.7.3 02 Dec 2014 M1 U1 — Yes Details →
0.7.2 18 Jan 2014 M1 U1 — Yes Details →
0.7.1 17 Jan 2014 M1 U1 — Yes Details →
0.7.0 07 Dec 2013 M1 L1 U2 — Yes Details →
0.6.1 10 Mar 2013 M1 L1 U2 — Yes Details →
0.6.0 09 Mar 2013 M1 L1 U2 — Yes Details →
0.5.1 15 Dec 2012 M1 L1 U2 — Yes Details →
0.5.0 15 Dec 2012 M1 L1 U2 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2014 2
  • 2019 1
  • 2020 1
  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for rply

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2014-1938: Link Following in rply 5.5 medium 0.7.4 11 Mar 2020
CVE-2014-1938: Insecure Creation of Temporary Files in python-rply N/A unrated 0.7.4 21 Nov 2019
CVE-2014-1604: RPLY Predictable Tmpfile Names Allows Cache Spoofing N/A low 0.7.1 17 May 2022
CVE-2014-1604: rply - Spoofing Cache Data N/A unrated fc9bbcd25b0b4f09bbd6339f710ad24c129d5d7c 28 Jan 2014
CVE-2014-1604: rply Package Vulnerability Allows Cache Data Spoofing N/A unrated No fix published 28 Jan 2014

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 rply

Is rply safe to use?

Vulert records 5 vulnerabilities for rply in PyPI: 0 critical, 0 high, 1 medium and 1 low, plus 3 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is rply's Vulert package health score?

Vulert scores rply 60/100, which reads as usable, but worth attention. 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 rply affected?

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

Which version of rply should I use?

0.7.8 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 rply have?

5 vulnerabilities are recorded for rply in the PyPI ecosystem: 0 critical, 0 high, 1 medium and 1 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 rply vulnerabilities disclosed?

0 vulnerabilities were recorded for rply in the last 12 months, and the oldest entry in this database dates to 28 Jan 2014. 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 rply 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 rply for upcoming vulnerabilities?

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