{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-21864 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-21864 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-21864 is a medium-severity denial of service vulnerability in valkey-io valkey-bloom, published on 24 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-21864 and fix it if it is affected.\n\nWhat it is: CVE-2026-21864 is a medium-severity denial of service vulnerability in valkey-io valkey-bloom, published on 24 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-21864 in the wild and no public exploit code.\n\nAffected product: valkey-io valkey-bloom. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-21864/ (Markdown: https://insights.sbomify.com/CVE-2026-21864/index.md)","id":"CVE-2026-21864","markdown":"https://insights.sbomify.com/CVE-2026-21864/index.md","name":"CVE-2026-21864","record":{"aliases":["GHSA-mc2g-h759-3qw2"],"analysis":{"component_type":"database","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Valkey Bloom module","requires_auth":"low_privilege","summary":"A remote attacker can crash the Valkey database server by sending a malformed RESTORE command to the Bloom module.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"valkey-bloom","vendor":"lfprojects"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Remote DoS from malformed RESTORE command","id":"CVE-2026-21864","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Discourse topic conversion permission vulnerability for moderators","id":"CVE-2026-21865"},"packages":[],"prev":{"headline":"Malformed Valkey Cluster bus message can lead to Remote DoS","id":"CVE-2026-21863"},"products":["valkey-bloom"],"published":"2026-02-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-26","vendors":["valkey-io"]},"summary":"A remote attacker can crash the Valkey database server by sending a malformed RESTORE command to the Bloom module.","url":"https://insights.sbomify.com/CVE-2026-21864/"}