VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

rediswrapper: vulnerability history, versions and safety

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

i
3 vulnerabilities recorded C1 U2
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 rediswrapper vulnerabilities

Vulert verdict on rediswrapper 0.4.0.post1 i

Updated on 23 Oct 2026

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

Package health score 50/100
  • Security Some issues to review
  • Maintenance Maintaining
  • Popularity Little adoption
  • Community Inactive

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

  • Current release 0.4.0.post1 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 20 Nov 2019 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Stars 10 i
  • OpenSSF scorecard 2/10 i
  • Last release 45 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.

01 Versions

Which versions are affected

Every version Vulert tracks for rediswrapper, 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.4.0.post1 09 Jan 2023 none MIT — Details →
0.4.0 09 Jan 2023 none MIT — Details →
0.3.0 05 Oct 2019 none MIT — Details →
0.2.1 07 May 2017 C1 U2 MIT Yes Details →
0.2.0 04 May 2017 C1 U2 MIT Yes Details →
0.1.0 04 May 2017 C1 U2 MIT Yes Details →

All 6 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

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

03 Vulnerabilities

Recorded vulnerabilities for rediswrapper

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2019-17206: Uncontrolled Deserialization of Pickled Object in rediswrapper 9.8 critical 0.3.0 20 Nov 2019
CVE-2019-17206: Uncontrolled Deserialization in Frost Ming Redis Wrapper N/A unrated 0.3.0 05 Oct 2019
CVE-2019-17206: Uncontrolled Deserialization in Frost Ming Redis Wrapper N/A unrated 0.3.0 05 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 rediswrapper

Is rediswrapper safe to use?

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

Vulert scores rediswrapper 50/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).

Is the latest version of rediswrapper affected?

No. 0.4.0.post1, 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 rediswrapper should I use?

0.4.0.post1 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 rediswrapper have?

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

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

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