What it is
In-memory stores such as Redis and Memcached.
Why it is risky
These are usually unauthenticated by default — exposure lets attackers read/write sessions & keys (even RCE) or wipe data.
What to do
Bind to 127.0.0.1 / private network, set requirepass·ACLs, and allow only internal hosts through the firewall.
Is it listening on your server?
Linux
ss -ltnp 'sport = :6379'Known vulnerabilities in Redis
| CVE | Title | CVSS | Exploited | EPSS | Published |
|---|---|---|---|---|---|
| CVE-2022-0543 | It was discovered, that redis, a persistent key-value database, due to a packaging issue, is prone to a (Debia... | 10.0 | KEV | 99.4% | 2022-02-19 |
| CVE-2025-49844 | Redis Lua Use-After-Free may lead to remote code execution | 10.0 | — | 2025-10-04 | |
| CVE-2023-41056 | Redis vulnerable to integer overflow in certain payloads | 8.1 | — | 2024-01-11 | |
| CVE-2025-62507 | Redis: Bug in XACKDEL may lead to stack overflow and potential RCE | 7.7 | — | 2025-11-05 | |
| CVE-2026-23479 | redis-server use-after-free in unblock client flow may allow remote code execution | 7.7 | — | 2026-05-06 | |
| CVE-2026-25243 | redis-server RESTORE invalid memory access may allow remote code execution | 7.7 | — | 2026-05-06 | |
| CVE-2021-32626 | Lua scripts can overflow the heap-based Lua stack in Redis | 7.5 | — | 2021-10-05 |
Track these versions on your own servers
InfraGuard collects installed software versions from every server and flags the ones with known vulnerabilities. Self-hosted — nothing leaves your network.