Skip to main content
VulnerabilityPublished Updated

CVE-2026-21864: valkey-bloom · Improper Input Validation

Affects valkey-bloomSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
valkey-iovalkey-bloomAffected
  • =< a68614b6e3845777d383b3a513cedcc08b3b7ccd
Fixed in–

AI-suggested

Organizations should immediately upgrade valkey-bloom to versions including or later than commit a68614b6e3845777d383b3a513cedcc08b3b7ccd, which contains the patch setting the VALKEYMODULE_OPTIONS_HANDLE_IO_ERRORS flag to properly handle RDB parsing errors. If upgrading is not immediately feasible, disabling the RESTORE command in the Valkey configuration is a practical interim mitigation to prevent exploitation. Network-level controls such as firewall rules or access control lists should restrict access to the Valkey server ports to trusted hosts only, minimizing exposure to untrusted networks. Monitoring logs for unusual RESTORE command usage or assertion failures can help detect attempted exploitation. Additionally, implementing redundancy and failover mechanisms can reduce service impact in case of a crash. Regularly reviewing and applying security updates for Valkey modules is essential to maintain resilience against similar vulnerabilities.

Description

Valkey-Bloom is a Rust based Valkey module which brings a Bloom Filter (Module) data type into the Valkey distributed key-value database. Prior to commit a68614b6e3845777d383b3a513cedcc08b3b7ccd, a specially crafted `RESTORE` command can cause Valkey to hit an assertion, causes the server to shutdown. Valkey modules are required to handle errors in RDB parsing by using `VALKEYMODULE_OPTIONS_HANDLE_IO_ERRORS` flag. If this flag is not set, errors encountered during parsing result in a system assertion which shuts down the system. Even though the Valkey-bloom module correctly handled the parsing, it did not originally set the flag. Commit a68614b6e3845777d383b3a513cedcc08b3b7ccd contains a patch. One may mitigate this defect by disabling the `RESTORE` command if it is unused by one's application.

References

Community reviews

Loading reviews…