CVE-2025-21605

Redis DoS Vulnerability due to unlimited growth of output buffers abused by unauthenticated client

HIGH
7.5
CVSS Score
Published: April 23, 2025 at 03:38 PM UTC
Updated: June 17, 2026 at 08:43 AM UTC
3 products affected across 3 vendorsDebian LinuxRedisValkey

Using redis by redis?

Get instant alerts when new vulnerabilities affect redis - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.9%
SSVC
No known exploit

Description

Redis is an open source, in-memory database that persists on disk. In versions starting at 2.6 and prior to 7.4.3, An unauthenticated client can cause unlimited growth of output buffers, until the server runs out of memory or is killed. By default, the Redis configuration does not limit the output buffer of normal clients (see client-output-buffer-limit). Therefore, the output buffer can grow unlimitedly over time. As a result, the service is exhausted and the memory is unavailable. When password authentication is enabled on the Redis server, but no password is provided, the client can still cause the output buffer to grow from "NOAUTH" responses until the system will run out of memory. This issue has been patched in version 7.4.3. An additional workaround to mitigate this problem without patching the redis-server executable is to block access to prevent unauthenticated users from connecting to Redis. This can be done in different ways. Either using network access control tools like firewalls, iptables, security groups, etc, or enabling TLS and requiring users to authenticate using client side certificates.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

7.2.4 ≤ v < 7.2.98.0.0 ≤ v < 8.0.38.1.0 ≤ v < 8.1.1
Affected range stops below 7.2.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 8.0.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 8.1.1, so it looks safe — our inference, not a vendor statement
v < 7.4.32.6.0 ≤ v < 6.2.187.0 ≤ v < 7.2.87.4.0 ≤ v < 7.4.3
Affected range stops below 7.4.3, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHGitHub_M
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-770

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card