{"answers":{"affected":"1 open source package ship an affected version, including valkey. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-21863 in the wild and no public exploit code.","fix":"Upgrade valkey to a fixed version for your release line: 7.2.12, 8.0.7, 8.1.6 or 9.0.2.","what":"CVE-2026-21863 is a high-severity denial of service vulnerability in valkey-io valkey, published on 23 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-21863 and fix it if it is affected.\n\nWhat it is: CVE-2026-21863 is a high-severity denial of service vulnerability in valkey-io valkey, published on 23 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-21863 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- valkey (Bitnami): affected all versions; fixed in 7.2.12, 8.0.7, 8.1.6, 9.0.2\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-21863/ (Markdown: https://insights.sbomify.com/CVE-2026-21863/index.md)","id":"CVE-2026-21863","markdown":"https://insights.sbomify.com/CVE-2026-21863/index.md","name":"CVE-2026-21863","record":{"aliases":["ALPINE-CVE-2026-21863","AZL-78320","BELL-CVE-2026-21863","BIT-valkey-2026-21863","DEBIAN-CVE-2026-21863","GHSA-c677-q3wr-gggq","RHSA-2026:8753"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Valkey database","requires_auth":"none","summary":"A remote attacker can crash the Valkey database by sending a malformed cluster bus message, requiring an upgrade to patched versions.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"valkey","vendor":"lfprojects"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"Valkey is a distributed key-value database. Prior to versions 9.0.2, 8.1.6, 8.0.7, and 7.2.12, a malicious actor with access to the Valkey clusterbus port can send an invalid packet that may cause an out bound read, which might result in the system crashing. The Valkey clusterbus packet processing code does not validate that a clusterbus ping extension packet is located within buffer of the clusterbus packet before attempting to read it. Versions 9.0.2, 8.1.6, 8.0.7, and 7.2.12 fix the issue. As an additional mitigation, don't expose the cluster bus connection directly to end users, and protect the connection with its own network ACLs.","ecosystems":["Bitnami","Red Hat:hummingbird:1"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Malformed Valkey Cluster bus message can lead to Remote DoS","id":"CVE-2026-21863","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":7,"n_references":1,"next":{"headline":"Remote DoS from malformed RESTORE command","id":"CVE-2026-21864"},"packages":[{"ecosystem":"Bitnami","fixed":["7.2.12","8.0.7","8.1.6","9.0.2"],"introduced":["0","8.0.0","8.1.0","9.0.0"],"last_affected":[],"package":"valkey","purl":"pkg:bitnami/valkey","source":"BIT-valkey-2026-21863"},{"ecosystem":"Red Hat:hummingbird:1","fixed":["0:9.0.3-1.2.hum1"],"introduced":["0"],"last_affected":[],"package":"valkey","purl":"pkg:rpm/redhat/valkey","source":"RHSA-2026:8753"},{"ecosystem":"Red Hat:hummingbird:1","fixed":["0:9.0.3-1.2.hum1"],"introduced":["0"],"last_affected":[],"package":"valkey-compat-redis","purl":"pkg:rpm/redhat/valkey-compat-redis","source":"RHSA-2026:8753"},{"ecosystem":"Red Hat:hummingbird:1","fixed":["0:9.0.3-1.2.hum1"],"introduced":["0"],"last_affected":[],"package":"valkey-compat-redis-devel","purl":"pkg:rpm/redhat/valkey-compat-redis-devel","source":"RHSA-2026:8753"},{"ecosystem":"Red Hat:hummingbird:1","fixed":["0:9.0.3-1.2.hum1"],"introduced":["0"],"last_affected":[],"package":"valkey-devel","purl":"pkg:rpm/redhat/valkey-devel","source":"RHSA-2026:8753"},{"ecosystem":"Red Hat:hummingbird:1","fixed":["0:9.0.3-1.2.hum1"],"introduced":["0"],"last_affected":[],"package":"valkey-doc","purl":"pkg:rpm/redhat/valkey-doc","source":"RHSA-2026:8753"},{"ecosystem":"Red Hat:hummingbird:1","fixed":["0:9.0.3-1.2.hum1"],"introduced":["0"],"last_affected":[],"package":"valkey-rdma","purl":"pkg:rpm/redhat/valkey-rdma","source":"RHSA-2026:8753"}],"prev":{"headline":"RustFS sourceIp bypass via spoofed X-Forwarded-For/Real-IP headers","id":"CVE-2026-21862"},"products":["valkey"],"published":"2026-02-23","related":[{"cvss_score":10,"headline":"Redis Lua Use-After-Free may lead to remote code execution","id":"CVE-2025-49844","kev_date_added":null,"published":"2025-10-03"},{"cvss_score":8.5,"headline":"Valkey Affected by RESP Protocol Injection via Lua error_reply","id":"CVE-2025-67733","kev_date_added":null,"published":"2026-02-23"},{"cvss_score":7.5,"headline":"Valkey has Pre-Authentication DOS from malformed RESP request","id":"CVE-2026-27623","kev_date_added":null,"published":"2026-02-23"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Red Hat","prefix":"RHSA"},{"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-15","vendors":["valkey-io"]},"summary":"A remote attacker can crash the Valkey database by sending a malformed cluster bus message, requiring an upgrade to patched versions.","url":"https://insights.sbomify.com/CVE-2026-21863/"}