CVE-2025-32023
Redis 2.8.0 – 6.2.19
Raw vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2025-32023 is a high-severity Integer Overflow to Buffer Overflow (CWE-680) vulnerability in Redis Redis. Its CVSS base score is 7.0 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 10% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
Redis is an open source in-memory database that persists on disk. CVE-2025-32023 is a stack/heap out-of-bounds write in hyperloglog operations that affects all versions from 2.8 through 8.0.2, 7.4.4, 7.2.9, and 6.2.18. An authenticated user who can supply a specially crafted string can trigger the flaw, which is tracked as CWE-680 and carries a CVSS 3.1 score of 7.0.
Because the attack requires local access and an existing authenticated session, a successful exploit can result in remote code execution on the Redis server. The issue is believed to affect every Redis release that implements hyperloglog commands.
Patches are available in Redis 8.0.3, 7.4.5, 7.2.10, and 6.2.19. The project also documents an ACL-based workaround that blocks all HLL commands without requiring a server binary update. The associated GitHub commits and release tags confirm the fixes and the command-restriction mitigation.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-20233
Vulnerability Data
Redis is an open source, in-memory database that persists on disk. From 2.8 to before 8.0.3, 7.4.5, 7.2.10, and 6.2.19, an authenticated user may use a specially crafted string to trigger a stack/heap out of bounds write on hyperloglog operations,…
more
potentially leading to remote code execution. The bug likely affects all Redis versions with hyperloglog operations implemented. This vulnerability is fixed in 8.0.3, 7.4.5, 7.2.10, and 6.2.19. An additional workaround to mitigate the problem without patching the redis-server executable is to prevent users from executing hyperloglog operations. This can be done using ACL to restrict HLL commands.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and analysis (static, dynamic, fuzzing) finds integer-overflow-to-allocation defects before deployment.
Mandates documented development standards and tools that enforce secure coding rules against unsafe integer arithmetic.
Requires engineering principles such as safe arithmetic and bounds-checked allocation that directly stop integer overflow during memory-size computation.
Validates untrusted size/offset inputs before they reach allocation calculations, structurally blocking the integer overflow path.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prevent integer-overflow flaws during development, but eliminating only this CWE covers only part of the broad control intent.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect integer-overflow-to-buffer-overflow conditions during development.
Secure development life cycle mandates practices that can catch integer overflows before deployment.
Application security requirements can specify safe integer handling and bounds checking.
Secure architecture principles encourage use of safe arithmetic libraries and overflow detection.
Secure coding standards directly require prevention of integer overflows that lead to buffer overflows.