Use-After-Free in Redis (CVE-2026-23479, CVSS 8.8)

Summary

Vulnerability in Redis (CVE-2026-23479). Successful exploitation can lead to full system takeover. Exploitable via processCommandAndResetClient.

Original description

The description as published by the source.

Redis is an in-memory data structure store. In redis-server from 7.2.0 until 8.6.3, the unblock client flow does not handle an error return from processCommandAndResetClient when re-executing a blocked command. If a blocked client is evicted during this flow, an authenticated attacker can trigger a use-after-free that may lead to remote code execution. This has been patched in version 8.6.3.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-23479 has been found in Redis.
Attackers can target a specific entry point like processCommandAndResetClient over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Redis CVE-2026-23479" on the vendor's site.

CVE-2026-23479 (Redis) — CWE-416 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: processCommandAndResetClient
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Use-after-free (CWE-416) exists in Redis. Attackers reach the vulnerable code path via processCommandAndResetClient.

📍 Affected scope

Check the vendor advisory for the affected versions of Redis. Attack surface: processCommandAndResetClient.

🔥 Severity

Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで Redis を使っているサービスとバージョンを洗い出す。
2
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Bitnami keydb

[{"type":"SEMVER","events":[{"introduced":"7.2.0"},{"fixed":"7.2.14"},{"introduced":"7.3.0"},{"fixed":"7.4.9"},{"introduced":"8.0.0"},{"fixed":"8.2.6"},{"introduced":"8.3.0"},{"fixed":"8.4.3"},{"introduced":"8.5.0"},{"fixed":"8.6.3"}]}]

Bitnami redis

[{"type":"SEMVER","events":[{"introduced":"7.2.0"},{"fixed":"7.2.14"},{"introduced":"7.3.0"},{"fixed":"7.4.9"},{"introduced":"8.0.0"},{"fixed":"8.2.6"},{"introduced":"8.3.0"},{"fixed":"8.4.3"},{"introduced":"8.5.0"},{"fixed":"8.6.3"}]}]

Bitnami valkey

[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"7.2.13"},{"introduced":"8.0.0"},{"fixed":"8.0.8"},{"introduced":"8.1.0"},{"fixed":"8.1.7"},{"introduced":"9.0.0"},{"fixed":"9.0.4"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

Alpine Linux ALPINE-CVE-2026-23479 valkey Fixed in: 7.2.13-r0
BellSoft Alpaquita BELL-CVE-2026-23479 redis Fixed in: 7.2.14-r0
Debian DEBIAN-CVE-2026-23479 redis
Ubuntu UBUNTU-CVE-2026-23479 redis

Use-After-Free in Redis (CVE-2026-23479)