CVE-2026-21863: Malformed Valkey Cluster bus message can lead to Remote DoS

Published Feb 23, 2026
·
Updated

Malformed Valkey Cluster bus message can lead to Remote DoS

Other sources

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.

NVD

Affected Software

9 affected componentsFixes available
Valkey Valkey<9.0.2
Valkey Valkey<8.1.6
Valkey Valkey<8.0.7
Valkey Valkey<7.2.12
Lfprojects Valkey<7.2.12
Lfprojects Valkey>=8.0.0<8.0.7
Lfprojects Valkey>=8.1.0<8.1.6
Lfprojects Valkey>=9.0.0<9.0.2
Microsoft azl3 valkey 8.0.6-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 9.0.2
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 8.1.6
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 8.0.7
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 7.2.12
  5. Compensating control

    Do not expose the Valkey cluster bus connection/clusterbus port directly to end users; instead, protect it with its own network ACLs so only trusted clients/systems can access the clusterbus port.

Event History

Feb 23, 2026
CVE Published
via MITRE·07:41 PM
Data Sourced
via MITRE·07:41 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:28 PM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via Red Hat·09:03 PM
DescriptionSeverityAffected Software
Feb 26, 2026
Data Sourced
via Microsoft·09:01 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·09:01 AM
DescriptionSeverity
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-21863?

CVE-2026-21863 has a high severity level due to the potential for system crashes caused by malformed packets.

2

How do I fix CVE-2026-21863?

To remediate CVE-2026-21863, upgrade to Valkey versions 9.0.2, 8.1.6, 8.0.7, or 7.2.12 or later.

3

Who is affected by CVE-2026-21863?

CVE-2026-21863 affects users running Valkey versions earlier than 9.0.2, 8.1.6, 8.0.7, or 7.2.12.

4

What causes CVE-2026-21863?

CVE-2026-21863 is caused by a malicious actor sending an invalid packet through the Valkey clusterbus port.

5

Can CVE-2026-21863 lead to data loss?

While CVE-2026-21863 primarily causes system crashes, it may also lead to temporary service disruption and potential data loss depending on the circumstances.

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