CVE-2026-21864: Remote DoS from malformed RESTORE command

Published Feb 24, 2026
·
Updated

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

2 affected components
valkey/valkey-bloom<a68614b6e3845777d383b3a513cedcc08b3b7ccd
Lfprojects Valkey-bloom<1.0.1

Event History

Feb 24, 2026
CVE Published
via MITRE·12:24 AM
Data Sourced
via MITRE·12:24 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·01:16 AM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-21864?

CVE-2026-21864 is classified as a remote denial-of-service (DoS) vulnerability.

2

How do I fix CVE-2026-21864?

To mitigate CVE-2026-21864, upgrade Valkey-Bloom to version a68614b6e3845777d383b3a513cedcc08b3b7ccd or later.

3

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.

4

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.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203