Redis on Linux: which version fixes what

What it is, and why it is on your server

Redis is an in-memory data store used for caching, sessions and queues. It is fast because it does very little, and historically that included doing very little about authentication.

Why its advisories behave the way they do

• An open Redis is a remote shell. With no password and no bind address, an attacker can write arbitrary files as the Redis user, which has been turned into an SSH key in authorized_keys and a cron job more times than any CVE on this list.
• It is usually installed as a dependency. Somebody adds a caching plugin, Redis arrives with it, and nobody treats it as a service with a configuration.
• Lua sandbox escapes are the interesting CVEs. Several advisories are about breaking out of the embedded scripting engine, which matters if anything untrusted can run a script.

Check what you are actually running

The version that matters is the package version, not the upstream one. Distributions backport security fixes without changing the number before the dash, so a release that looks years old is frequently fully patched, and the revision after the dash is the only part that tells you.

dpkg-query -W -f='${Package} ${Version}\n' redis-server redis-tools 2>/dev/null

rpm -q redis

The first check is not the version. `ss -lntp | grep 6379` and `grep -E "^(bind|requirepass|protected-mode)" /etc/redis/redis.conf` will tell you more about your exposure than any advisory list.

Fixed versions, per distribution

Each distribution patches on its own schedule and under its own version scheme, so the same CVE has a different answer on each of them. These come from the distributions’ own advisory data, asked per release. Where a release has no fixed version, that is what the advisory says, not a gap in the data.

Advisory data last refreshed 26 September 2026. It is re-read daily.

What this page does not tell you

It does not tell you whether your server is affected. A CVE applying to a package is not the same as a CVE applying to your installation: the fix may already be backported into what you are running, the vulnerable module may not be loaded, or the service may not be reachable from anywhere that matters. Answering that needs the versions on your machine, not a list.

It also carries no count of how many servers are affected. SecAI monitors a small fleet, and a percentage drawn from it would be arithmetic on a sample too small to mean anything. When that changes, the number will appear here and the page will say when it started.

Read next