Read the docs

Multi-bulk commands enable denial of service in Redis

Priority MEDIUM 46Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Attack requirements
Present
Impact type
—
Confidentiality · integrity · availability
None · None · High
Fix status
No fix listed

Attack profile from CVSS 4.0 · GHSA-2r7g-8hpc-rpq9. Fix status from GitHub.

Summary

Redis versions up to and including 8.0 are affected. Multi-bulk commands sent by clients over the Redis commands protocol can impact the availability and performance of the database. An authenticated user with access to the database can cause denial of service. Redis does not consider this a vulnerability under its security model and published it as a security advisory.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

Description from the GitHub advisory

From time to time we discover situations where the Redis application will allow a logged-in user to cause a denial-of-service or otherwise impact the performance or availability of the database they have access to, which can happen without explicitly violating the Redis Security Model. In some cases, such as CVE-2024-31227 and CVE-2024-31228, we elect to fix these denial-of-service possibilities in code as they result from error conditions. These decisions make tradeoffs between potential risks on the one hand, and the potential for introducing breaking changes, impacting database performance, and other considerations on the other. Recently, security researcher Gabriele Digregorio brought a similar potential denial-of-service issue to our attention. Based on Gabriele Digregorio’s research, and validated through our own analysis, this issue relies on abuse or misuse of the commands network protocol built into Redis and requires the user to be successfully authenticated. As such, it does not violate the Redis Security Model (therefore, we do not consider it a vulnerability and do not assign a CVE ID), but could still be used to cause unintended or unexpected impact to availability. Our assessment is that implementing an application change to prevent this possibility would negatively impact legitimate functionality and performance of Redis. As a result, we do not have a fix planned for this issue and are instead opting to publish this Security Advisory to bring it to the attention of users. As always, we encourage Redis operators and admins to review our recommended security practices, and enforce strong access controls or integration with corporate identity provider solutions whenever possible.

Why it matters now

Fix No fix listed No fixed version in the sources yet

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—redis<= 8.0—No fix listedGHSA-2r7g-8hpc-rpq9
  • redis Vendor— Affected <= 8.0 Fixed in — No fix listed GHSA-2r7g-8hpc-rpq9

Remediation

The sources list no fixed version for redis. Redis recommends enforcing strong access controls or integration with a corporate identity provider.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

Timeline

  1. 2026-11-12 Threatist record created from GHSA-2r7g-8hpc-rpq9

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences