dbcve.org
RedisDatabase / datastore

CVE-2025-32023

HIGH · 7.8 CVSS v3.1 Published 2025-07-07
Fix available
A fix is available. Upgrade to 6.2.19 / 7.2.10 or later.
See remediation →
80/100
Remediation priority · High
Public exploit Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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, 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RedisDatabase / datastore
Affected:>= 2.8.0, < 6.2.19>= 7.2.0, < 7.2.10>= 7.4.0, < 7.4.5>= 8.0.0, < 8.0.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.2.19 / 7.2.10 / 7.4.5 or later
Fixed in 6.2.197.2.107.4.5
Vendor patch github.com →
Recommended fix High confidence

Redis 6.2.19, 7.2.10, 7.4.5, or 8.0.3 (select based on current major version)

  1. Identify the currently running Redis version using `redis-server --version` or `INFO` command
  2. Determine the appropriate upgrade target based on current version: for 7.4.x upgrade to 7.4.5, for 7.2.x upgrade to 7.2.10, for 6.2.x upgrade to 6.2.19, for 8.0.x upgrade to 8.0.3
  3. For package-managed installations: run `apt-get update && apt-get install redis-server` (Debian/Ubuntu) or `yum update redis` (RHEL/CentOS)
  4. For source installations: download the appropriate release from redis.io/download and rebuild
  5. After upgrade, restart the Redis service using `systemctl restart redis` or the equivalent for your setup
  6. Verify the new version is running with `redis-server --version`
  7. Optionally, verify the vulnerability is fixed by checking that HLL operations no longer cause out-of-bounds writes with the reported input
Caveat Redis minor version upgrades are typically backward compatible; however, review release notes for any deprecated commands or behavioral changes before upgrading in production

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32023 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-32023 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data