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

High CVSS 7.5

CVE id
CVE-2025-21605
Published
Last modified

Affected packages

PackageAffected versionsFixed in
Redis
Runtimes and servers
>= 2.6.0, < 6.2.18
>= 7.0, < 7.2.8
>= 7.4.0, < 7.4.3
6.2.18, 7.2.8, 7.4.3
Valkey
Runtimes and servers
>= 7.2.4, < 7.2.9
>= 8.0.0, < 8.0.3
>= 8.1.0, < 8.1.1
7.2.9, 8.0.3, 8.1.1

How to fix it

Redis (Runtimes and servers)

Upgrade Redis to the fixed release of the line you run: 6.2.18, 7.2.8, 7.4.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.

Valkey (Runtimes and servers)

Upgrade Valkey to the fixed release of the line you run: 7.2.9, 8.0.3, 8.1.1.

valkey-server --version
  • Install the patched Valkey release of your series (the valkey image tag).

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. 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.

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.