CVE-2025-32023: Redis is an open source, in-memory database that persists on disk.

High CVSS 7.8

CVE id
CVE-2025-32023
Published
Last modified

Affected packages

PackageAffected versionsFixed in
Redis
Runtimes and servers
>= 2.8.0, < 6.2.19
>= 7.2.0, < 7.2.10
>= 7.4.0, < 7.4.5
>= 8.0.0, < 8.0.3
6.2.19, 7.2.10, 7.4.5, 8.0.3

How to fix it

Upgrade Redis to the fixed release of the line you run: 6.2.19, 7.2.10, 7.4.5, 8.0.3.

redis-server --version
  • Install the patched Redis release of your series (the redis image tag or your packages) and restart it; on a managed service, apply the provider's maintenance update.

A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.

Details

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.

References

Am I affected?

Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About this data

Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.