# CVE-2026-66373: Use after free in Redis

> An authenticated attacker can achieve remote code execution in Redis by exploiting a double free vulnerability in the RESTORE command handling.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jul 2026
- **Updated:** 7 Aug 2026
- **Also known as:** AZL-93408, CLSA-2026-1788963269, CLSA-2026-1789375350, DEBIAN-CVE-2026-66373, GHSA-c964-568j-vxx7, OESA-2026-3298, SUSE-SU-2026:3636-1, SUSE-SU-2026:3637-1, SUSE-SU-2026:3638-1, SUSE-SU-2026:3639-1, UBUNTU-CVE-2026-66373

## What is CVE-2026-66373?

CVE-2026-66373 is a high-severity use after free vulnerability in Redis, published on 25 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

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

Weakness: CWE-415 (Double Free)

## Which versions are affected by CVE-2026-66373?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `redis` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 6.2.6-150400.3.49.1 |
| `redis` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 6.2.6-150400.3.49.1 |
| `redis` | SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 6.2.6-150400.3.49.1 |
| `redis7` | SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 7.0.8-150500.3.34.1 |
| `redis` | SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 6.2.6-150400.3.49.1 |
| `redis7` | SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 7.0.8-150500.3.34.1 |
| `redis` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 6.2.6-150400.3.49.1 |
| `redis` | SUSE:Linux Enterprise Server 15 SP5-LTSS | All versions | 6.2.6-150400.3.49.1 |
| `redis7` | SUSE:Linux Enterprise Server 15 SP5-LTSS | All versions | 7.0.8-150500.3.34.1 |
| `redis` | SUSE:Linux Enterprise Server 15 SP6-LTSS | All versions | 7.2.4-150600.3.27.1 |
| `redis7` | SUSE:Linux Enterprise Server 15 SP6-LTSS | All versions | 7.0.8-150600.8.28.1 |
| `redis` | SUSE:Linux Enterprise Server for SAP Applications 15 SP4 | All versions | 6.2.6-150400.3.49.1 |
| `redis` | SUSE:Linux Enterprise Server for SAP Applications 15 SP5 | All versions | 6.2.6-150400.3.49.1 |
| `redis7` | SUSE:Linux Enterprise Server for SAP Applications 15 SP5 | All versions | 7.0.8-150500.3.34.1 |
| `redis` | SUSE:Linux Enterprise Server for SAP Applications 15 SP6 | All versions | 7.2.4-150600.3.27.1 |
| `redis7` | SUSE:Linux Enterprise Server for SAP Applications 15 SP6 | All versions | 7.0.8-150600.8.28.1 |

## How do I fix CVE-2026-66373?

Upgrade to a fixed version.

## Is CVE-2026-66373 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-66373 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-66373 and fix it if it is affected.

What it is: CVE-2026-66373 is a high-severity use after free vulnerability in Redis, published on 25 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-66373 exists.

Affected product: Redis. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-66373/ (Markdown: https://insights.sbomify.com/CVE-2026-66373/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-66373
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-66373
- OSV: https://osv.dev/vulnerability/CVE-2026-66373

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-66373/
Summaries are generated and may contain mistakes; the official description above is the record.