Vulnerability Database · PyPI · rply · Version
rply 0.7.1
0.7.1 is affected by 3 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 0.7.8.
Critical 0 High 0 Medium 1 Low 0 Unrated 2
-
Released 17 Jan 2014
Licence BSD-3-Clause
Also known from other sources 2
Newer releases 13
Database updated 23/Oct/2026
Release and licence data published by PyPI. 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 Vulnerabilities affecting this version
rply 0.7.1 vulnerabilities
3 vulnerabilities cover rply 0.7.1. Open the full list 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 Package Vulnerability Allows Cache Data Spoofing | N/A unrated | No fix published | 28 Jan 2014 |
Looking for another version, or everything Vulert holds for rply?
Questions
About rply 0.7.1
Is rply 0.7.1 vulnerable?
Yes. 3 vulnerabilities in the Vulert database cover rply 0.7.1: 0 critical, 0 high, 1 medium and 0 low, plus 2 not yet rated. The upgrade Vulert recommends is 0.7.8, and each entry above names the fixed version to move to.
Which version of rply should I use instead of 0.7.1?
0.7.8 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 0.7.1 the latest release of rply?
No. 0.7.1 was published 17 Jan 2014, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
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.