VulertSecurity VulertSecurity

Vulnerability Database · Bitnami · Package report

keydb: vulnerability history, versions and safety

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

i
48 vulnerabilities recorded C3 H25 M15 L5
i
6 with no fix published

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

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

Most recent disclosure 07 May 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all keydb vulnerabilities

Vulert verdict on keydb i

Updated on 23 Oct 2026

Careful: 6 of the 48 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 48 vulnerabilities on record across 1 year, 6 in the last year.

What to do: Plan around the 6 vulnerabilities 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 48 over 1 year · 6 in the last year i
  • Latest disclosure 07 May 2026 i
  • Highest CVSS n/a i
  • With no published fix 6 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 8.0.0 up to 8.2.6 (exclusive) 2
from 8.2.0 up to 8.2.3 (exclusive) 1
from 7.2.0 up to 7.2.14 (exclusive) 2
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.3.4 (exclusive) 2
from 2.2.5 up to 6.3.4 (exclusive) 1
from 2.6.0 up to 6.3.4 (exclusive) 1
from 2.8.0 up to 6.3.4 (exclusive) 1
up to 6.2.22 (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
from 7.0.0 onwards, no fix published yet 3
from 2.6.0 onwards, no fix published yet 1
all releases, no fix published yet 1
all releases, no fix published yet 1

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 30
  • 2025 13
  • 2026 5

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

03 Vulnerabilities

Recorded vulnerabilities for keydb

The 5 most severe of 48 vulnerabilities recorded for this package

Search all 48 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-25243: KeyDB RESTORE Command Vulnerability Leading to Remote Code Execution N/A high 6.2.22 07 May 2026
CVE-2025-62507: KeyDB Stack Overflow Vulnerability in XACKDEL Command N/A high 8.2.3 07 Nov 2025
CVE-2025-48367: KeyDB Redis DoS Vulnerability Due to Bad Connection Error Handling N/A high 6.3.4 09 Jul 2025
CVE-2025-32023: KeyDB Redis Hyperloglog Commands Vulnerability Leading to Remote Code Execution N/A high 6.3.4 09 Jul 2025
CVE-2024-46981: KeyDB Remote Code Execution Vulnerability via Lua Script Manipulation N/A high 6.3.4 08 Jan 2025

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 keydb

Is keydb safe to use?

Vulert records 48 vulnerabilities for keydb in Bitnami: 3 critical, 25 high, 15 medium and 5 low. 6 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does keydb have?

48 vulnerabilities are recorded for keydb in the Bitnami ecosystem: 3 critical, 25 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 keydb vulnerabilities disclosed?

6 vulnerabilities were recorded for keydb 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 keydb 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 keydb for upcoming vulnerabilities?

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