Service exhaustion via unlimited unauthenticated output buffers
Published Apr 23, 2025 · Updated Feb 10, 2026
Resource exhaustion in Redis 2.6 through 7.4.2 allows remote attackers to interrupt the service through unauthenticated connections. Normal-client output buffers have no default size limit, so repeated NOAUTH replies accumulate without throttling until memory is exhausted. Network access to the Redis endpoint is sufficient even when password authentication is enabled; the bounded consequence is server termination or loss of service.
Summary
What happened
Resource exhaustion in Redis 2.6 through 7.4.2 allows remote attackers to interrupt the service through unauthenticated connections. Normal-client output buffers have no default size limit, so repeated NOAUTH replies accumulate without throttling until memory is exhausted. Network access to the Redis endpoint is sufficient even when password authentication is enabled; the bounded consequence is server termination or loss of service.
The record
- CVE
- CVE-2025-21605
- Published
- Apr 23, 2025
- Updated
- Feb 10, 2026
- Vendor
- Redis
- Product
- Redis
- Classifications
- CWE-770, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 23, 2025CVE publishedPublication date reported by the CVE source.
- Feb 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 2.6, < 7.4.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo