CVE-2026-21864: Remote DoS from malformed RESTORE command
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 VALKEYMODULEOPTIONSHANDLEIOERRORS 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.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-21864?
CVE-2026-21864 is classified as a remote denial-of-service (DoS) vulnerability.
How do I fix CVE-2026-21864?
To mitigate CVE-2026-21864, upgrade Valkey-Bloom to version a68614b6e3845777d383b3a513cedcc08b3b7ccd or later.
What software versions are affected by CVE-2026-21864?
CVE-2026-21864 affects Valkey-Bloom versions prior to a68614b6e3845777d383b3a513cedcc08b3b7ccd and Lfprojects Valkey-Bloom versions up to but not including 1.0.1.
What kind of attack does CVE-2026-21864 enable?
CVE-2026-21864 allows an attacker to cause a denial-of-service condition via a specially crafted RESTORE command.
Is there any workaround for CVE-2026-21864?
Currently, the recommended approach is to upgrade to a patched version as there are no known workarounds for CVE-2026-21864.