VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

redis: vulnerability history, versions and safety

redis is a package in the PyPI ecosystem. Vulert records 7 vulnerabilities for it across 120 releases, from Jun 2022 to Jul 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
7 vulnerabilities recorded H1 M1 U5
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 redis vulnerabilities

Vulert verdict on redis 8.1.0 i

Updated on 23 Oct 2026

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

Package health score 60/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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 8.1.0 — affected i
  • Vulnerabilities on record 7 over 1 year · 0 in the last year i
  • Latest disclosure 15 Jul 2023 i
  • Highest CVSS 7.5 i
  • With no published fix 1 i
  • Depended on by 7,124 packages i
  • Stars 13,651 i
  • OpenSSF scorecard 6/10 i
  • Last release 2 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 redis, 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
8.1.0 30 Jul 2026 U2 MIT No Details →
8.0.1 23 Jun 2026 U2 MIT No Details →
7.4.1 05 Jun 2026 U2 MIT No Details →
7.3.1 05 Jun 2026 U2 MIT No Details →
7.2.2 05 Jun 2026 U2 MIT No Details →
8.0.0 28 May 2026 U2 MIT No Details →
8.0.0b2 17 Apr 2026 U2 MIT No Details →
8.0.0b1 08 Apr 2026 U2 MIT No Details →
7.4.0 24 Mar 2026 U2 MIT No Details →
7.3.0 06 Mar 2026 U2 MIT No Details →
7.2.1 25 Feb 2026 U2 MIT No Details →
7.2.0 16 Feb 2026 U2 MIT No Details →
7.1.1 09 Feb 2026 U2 MIT No Details →
7.1.0 19 Nov 2025 U2 MIT No Details →
7.0.1 27 Oct 2025 U2 MIT No Details →
7.0.0 22 Oct 2025 U2 MIT No Details →
7.0.0b3 07 Oct 2025 U2 MIT No Details →
7.0.0b2 26 Sep 2025 U2 MIT No Details →
7.0.0b1 09 Sep 2025 U2 MIT No Details →
6.4.0 07 Aug 2025 U2 MIT No Details →
6.3.0 05 Aug 2025 U2 MIT No Details →
5.3.1 25 Jul 2025 U2 MIT No Details →
6.1.1 02 Jun 2025 U1 MIT Yes Details →
6.2.0 28 May 2025 U2 MIT No Details →
6.1.0 13 May 2025 U1 MIT Yes Details →
6.0.0 30 Apr 2025 U1 MIT Yes Details →
5.3.0 30 Apr 2025 U1 MIT Yes Details →
6.0.0b2 07 Apr 2025 U1 MIT Yes Details →
6.0.0b1 24 Mar 2025 U1 MIT Yes Details →
5.3.0b5 11 Feb 2025 U1 MIT Yes Details →
5.3.0b4 23 Dec 2024 U2 MIT Yes Details →
5.3.0b3 20 Dec 2024 U2 MIT Yes Details →
5.3.0b1 20 Dec 2024 U2 MIT Yes Details →
5.2.1 06 Dec 2024 U2 MIT Yes Details →
5.2.0 24 Oct 2024 U2 MIT Yes Details →
5.1.1 04 Oct 2024 U2 MIT Yes Details →
5.1.0 27 Sep 2024 U2 MIT Yes Details →
5.0.8 30 Jul 2024 U2 MIT Yes Details →
5.0.7 26 Jun 2024 U2 MIT Yes Details →
5.1.0b7 20 Jun 2024 U2 MIT Yes Details →
5.0.6 13 Jun 2024 U2 MIT Yes Details →
5.1.0b6 06 Jun 2024 U2 MIT Yes Details →
5.0.5 06 Jun 2024 U2 MIT Yes Details →
5.1.0b5 08 May 2024 U2 MIT Yes Details →
5.0.4 23 Apr 2024 U2 MIT Yes Details →
5.0.3 10 Mar 2024 U2 MIT Yes Details →
5.1.0b4 29 Feb 2024 U2 MIT Yes Details →
5.0.2 28 Feb 2024 U2 MIT Yes Details →
5.1.0b3 15 Jan 2024 U2 MIT Yes Details →
5.1.0b2 07 Jan 2024 U2 MIT Yes Details →
5.1.0b1 01 Jan 2024 U2 MIT Yes Details →
5.1.0a1 16 Nov 2023 U2 MIT Yes Details →
5.0.1 26 Sep 2023 U2 MIT Yes Details →
5.0.0 15 Aug 2023 U2 MIT Yes Details →
5.0.0rc2 16 Jul 2023 U2 MIT Yes Details →
5.0.0rc1 27 Jun 2023 U3 MIT No Details →
4.6.0 25 Jun 2023 U3 MIT No Details →
5.0.0b4 28 May 2023 U3 MIT No Details →
4.5.5 08 May 2023 U3 MIT No Details →
5.0.0b3 04 May 2023 U3 MIT No Details →
5.0.0b2 24 Apr 2023 U3 MIT No Details →
4.4.4 29 Mar 2023 U3 MIT No Details →
4.5.4 29 Mar 2023 U3 MIT No Details →
5.0.0b1 23 Mar 2023 U3 MIT No Details →
4.3.6 22 Mar 2023 U4 MIT No Details →
4.4.3 22 Mar 2023 U4 MIT No Details →
4.5.3 22 Mar 2023 H1 U4 MIT No Details →
4.5.2 20 Mar 2023 H1 U5 MIT No Details →
4.5.1 08 Feb 2023 H1 U5 MIT No Details →
4.5.0 07 Feb 2023 H1 U5 MIT No Details →
4.4.2 11 Jan 2023 M1 U5 MIT No Details →
4.4.1 08 Jan 2023 M1 U5 MIT No Details →
4.4.0 04 Dec 2022 M1 U5 MIT No Details →
4.3.5 22 Nov 2022 U5 MIT No Details →
4.4.0rc4 10 Nov 2022 U4 MIT No Details →
4.4.0rc3 08 Nov 2022 U4 MIT No Details →
4.4.0rc2 29 Sep 2022 U4 MIT No Details →
4.4.0rc1 04 Aug 2022 U4 MIT No Details →
4.3.4 27 Jun 2022 U5 MIT No Details →
4.3.3 02 Jun 2022 U5 MIT No Details →
4.3.2 01 Jun 2022 U5 MIT No Details →
4.3.1 09 May 2022 U5 MIT No Details →
4.3.0 08 May 2022 U5 MIT No Details →
4.2.2 04 Apr 2022 U5 MIT No Details →
4.2.1 31 Mar 2022 U5 MIT No Details →
4.2.0 23 Mar 2022 U5 MIT No Details →
4.2.0rc3 14 Mar 2022 U3 MIT No Details →
4.2.0rc2 08 Mar 2022 U3 MIT No Details →
4.2.0rc1 22 Feb 2022 U3 MIT No Details →
4.1.4 16 Feb 2022 U3 MIT No Details →
4.1.3 08 Feb 2022 U3 MIT No Details →
4.1.2 27 Jan 2022 U3 MIT No Details →
4.1.1 17 Jan 2022 U3 MIT No Details →
4.1.0 26 Dec 2021 U3 MIT No Details →
4.1.0rc2 09 Dec 2021 U3 MIT No Details →
4.1.0rc1 25 Nov 2021 U3 MIT No Details →
4.0.2 22 Nov 2021 U3 MIT No Details →
4.0.1 17 Nov 2021 U3 MIT No Details →
4.0.0 15 Nov 2021 U3 MIT No Details →
4.0.0rc2 09 Nov 2021 U3 MIT No Details →
4.0.0rc1 04 Nov 2021 U3 — No Details →
4.0.0b3 26 Oct 2021 U3 — No Details →
4.0.0b2 26 Oct 2021 U3 — No Details →
4.0.0b1 17 Oct 2021 U3 — No Details →
3.5.3 01 Jun 2020 U3 — No Details →
3.5.2 14 May 2020 U3 — No Details →
3.5.1 09 May 2020 U3 — No Details →
3.5.0 29 Apr 2020 U3 — No Details →
3.4.1 02 Feb 2020 U3 — No Details →
3.4.0 31 Jan 2020 U3 — No Details →
3.3.11 13 Oct 2019 U3 — No Details →
3.3.10 10 Oct 2019 U3 — No Details →
3.3.9 10 Oct 2019 U3 — No Details →
3.3.8 19 Aug 2019 U3 — No Details →
3.3.7 13 Aug 2019 U3 — No Details →
3.3.6 06 Aug 2019 U3 — No Details →
3.3.5 02 Aug 2019 U3 — No Details →
3.3.4 30 Jul 2019 U3 — No Details →
3.3.3 30 Jul 2019 U3 — No Details →
3.3.2 29 Jul 2019 U3 — No Details →

The newest 120 of 169 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2023 6

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

03 Vulnerabilities

Recorded vulnerabilities for redis

The 5 most severe of 7 vulnerabilities recorded for this package

Search all 7 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-33105: Redis Memory Leak Vulnerability in PyPI Package 7.5 high 4a7a4e42db8ff757cdf3f4a824f66426036034ef 23 Jun 2022
CVE-2023-28859: redis-py Race Condition due to incomplete fix 6.5 high 4.5.4 26 Mar 2023
CVE-2021-31294: Redis SET Command Vulnerability Leading to Assertion Failure 5.9 medium 46f4ebbe842620f0976a36741a72482620aa4b48 15 Jul 2023
CVE-2023-28859: redis-py Race Condition vulnerability 3.7 medium 4.4.3 26 Mar 2023
CVE-2023-28859: Vulnerability in redis-py N/A unrated 4.4.4 26 Mar 2023

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 redis

Is redis safe to use?

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

What is redis's Vulert package health score?

Vulert scores redis 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 redis affected?

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

Which version of redis should I use?

8.1.0 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 redis have?

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

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

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