VulertSecurity VulertSecurity

Vulnerability Database · Bitnami · Package report

valkey: vulnerability history, versions and safety

valkey is a package in the Bitnami ecosystem. Vulert records 50 vulnerabilities for it across 36 affected ranges, from Aug 2024 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
50 vulnerabilities recorded C3 H27 M15 L5
i
1 with no fix published

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

See the unfixed vulnerabilities →
i
8 in the last 12 months

Most recent disclosure 24 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all valkey vulnerabilities

Vulert verdict on valkey i

Updated on 23 Oct 2026

Careful: one of the 50 vulnerabilities Vulert records for this package has no fix yet. Plan around that one, or apply its workaround. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 50 vulnerabilities on record across 2 years, 8 in the last year.

What to do: Plan around the 1 vulnerability with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 50 over 2 years · 8 in the last year i
  • Latest disclosure 24 Aug 2026 i
  • Highest CVSS n/a i
  • With no published fix 1 i

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

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
from 9.0.0 up to 9.0.3 (exclusive) 1
up to 8.0.4 (exclusive) 1
from 2.6.0 up to 8.0.0 (exclusive) 1
up to 7.2.14 (exclusive) 2
up to 7.2.13 (exclusive) 3
up to 7.2.12 (exclusive) 2
from 2.8.0 up to 7.2.10 (exclusive) 1
up to 7.2.10 (exclusive) 1
from 7.0.0 up to 7.2.9 (exclusive) 1
up to 7.2.7 (exclusive) 1
from 7.0.0 up to 7.2.7 (exclusive) 1
from 7.0.0 up to 7.2.6 (exclusive) 1
from 2.2.5 up to 7.2.6 (exclusive) 1
from 2.6.0 up to 7.2.6 (exclusive) 1
from 7.0.9 up to 7.0.15 (exclusive) 1
from 7.0.0 up to 7.0.13 (exclusive) 1
from 7.0.0 up to 7.0.12 (exclusive) 1
from 7.0.10 up to 7.0.11 (exclusive) 1
from 7.0.8 up to 7.0.10 (exclusive) 1
from 7.0.0 up to 7.0.5 (exclusive) 1
from 7.0.0 up to 7.0.4 (exclusive) 1
from 7.0.0 up to 7.0.1 (exclusive) 1
up to 6.2.20 (exclusive) 4
from 2.6.0 up to 6.2.14 (exclusive) 1
from 6.2.0 up to 6.2.9 (exclusive) 1
up to 6.2.8 (exclusive) 1
up to 6.2.7 (exclusive) 2
up to 6.2.0 (exclusive) 1
from 2.6.0 up to 6.0.20 (exclusive) 1
up to 6.0.19 (exclusive) 1
up to 6.0.18 (exclusive) 2
from 6.0.0 up to 6.0.17 (exclusive) 1
from 5.0.0 up to 5.0.14 (exclusive) 6
from 2.6.0 up to 5.0.14 (exclusive) 1
from 3.2.0 up to 5.0.14 (exclusive) 1
all releases, no fix published yet 1

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 30
  • 2025 12
  • 2026 8

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

03 Vulnerabilities

Recorded vulnerabilities for valkey

The 5 most severe of 50 vulnerabilities recorded for this package

Search all 50 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-27151: Valkey Redis-check-aof Stack Overflow Vulnerability N/A critical 7.2.9 31 May 2025
CVE-2026-21863: Valkey Remote DoS Vulnerability Due to Malformed Cluster Bus Messages N/A high 7.2.12 26 Feb 2026
CVE-2026-27623: Valkey Pre-Authentication DOS Vulnerability from Malformed RESP Request N/A high 9.0.3 26 Feb 2026
CVE-2025-32023: Redis Valkey Package Vulnerability Leading to Remote Code Execution N/A high 7.2.10 09 Jul 2025
CVE-2026-63639: Valkey Remote Code Execution Vulnerability Due to Use-After-Free in Stream Deserialization N/A high 7.2.14 24 Aug 2026

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 valkey

Is valkey safe to use?

Vulert records 50 vulnerabilities for valkey in Bitnami: 3 critical, 27 high, 15 medium and 5 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

How many vulnerabilities does valkey have?

50 vulnerabilities are recorded for valkey in the Bitnami ecosystem: 3 critical, 27 high, 15 medium and 5 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new valkey vulnerabilities disclosed?

8 vulnerabilities were recorded for valkey in the last 12 months, and the oldest entry in this database dates to 22 Aug 2024. 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 valkey 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 valkey for upcoming vulnerabilities?

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