Skip to main content

Valkey EUVDEUVD-2026-60822

| CVE-2026-56684 HIGH
Use After Free (CWE-416)
2026-08-18 GitHub_M
7.5
CVSS 3.1 · Vendor: GitHub_M
Share

Severity by source

Vendor (GitHub_M) PRIMARY
7.5 HIGH
AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
7.5 HIGH

Network-reachable TLS port justifies AV:N; race-condition timing requirement justifies AC:H; valid authentication is required so PR:L; full CIA:H reflects confirmed crash and plausible RCE impact.

3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE
HIGH
qualitative
Red Hat
7.5 HIGH
qualitative

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector
Network
Attack Complexity
High
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
Source Code Evidence Fetched
Aug 18, 2026 - 15:25 vuln.today
Analysis Generated
Aug 18, 2026 - 15:25 vuln.today
Patch available
Aug 18, 2026 - 15:02 EUVD
CVE Published
Aug 18, 2026 - 14:19 cve.org
HIGH 7.5

DescriptionCVE.org

Valkey is a distributed key-value database. Prior to 7.2.14, 8.0.10, 8.1.9, 9.0.5, and 9.1.1, Valkey's tlsProcessPendingData function iterates pending_list while an authenticated client can trigger CLIENT KILL, causing connTLSClose to delete the iterator's cached next node and producing a use-after-free that can crash the server or potentially allow remote code execution when TLS is enabled. This issue is fixed in versions 7.2.14, 8.0.10, 8.1.9, 9.0.5, and 9.1.1.

AnalysisAI

Use-after-free in Valkey's TLS connection handler allows an authenticated remote attacker to crash the server or potentially achieve remote code execution on TLS-enabled deployments. The flaw exists across all Valkey branches prior to 7.2.14, 8.0.10, 8.1.9, 9.0.5, and 9.1.1, confirmed via GitHub security advisory GHSA-53mc-f3m3-99vh and EUVD-2026-60822. No active exploitation has been confirmed (not in CISA KEV), but the full C:H/I:H/A:H CVSS impact and the RCE/Memory Corruption tags warrant prompt patching for any TLS-configured Valkey instance.

Technical ContextAI

Valkey (CPE: cpe:2.3:a:valkey-io:valkey) is an open-source distributed key-value store and actively maintained Redis fork. The vulnerability resides in src/tls.c within the tlsProcessPendingData function, which iterates over a pending_list of TLS connections awaiting I/O processing using a standard listIter. The iterator caches a pointer to the next list node at the start of each loop step. When an authenticated client issues a CLIENT KILL command targeting a concurrently iterated connection, the resulting internal call chain - freeClient → connTLSClose → listDelNode - frees the very node the iterator has cached, leaving a dangling pointer. CWE-416 (Use After Free) is the confirmed root cause class: subsequent dereference of the freed pointer produces either a server crash or, under controlled heap-layout conditions, arbitrary code execution. The fix in PR #4234 (commit 7cd5bcb) replaces the iterator with a pop-then-process loop that captures the list length at entry to bound iterations and re-appends deferred connections to the tail, eliminating the dangling-pointer window entirely.

RemediationAI

The primary remediation is to upgrade to one of the patched releases - 7.2.14, 8.0.10, 8.1.9, 9.0.5, or 9.1.1 - all available at the official GitHub release pages (https://github.com/valkey-io/valkey/releases/tag/7.2.14, /8.0.10, /8.1.9, /9.0.5, /9.1.1). The fix is confirmed by commit 7cd5bcb7575d750ec2de618db80da58680a10fe3 and GitHub advisory GHSA-53mc-f3m3-99vh. If an immediate upgrade is not feasible, disabling TLS entirely eliminates the vulnerable code path, though at the cost of encrypted transport - weigh this trade-off against network exposure. A narrower compensating control is to restrict CLIENT KILL privileges to only trusted administrative accounts, reducing which authenticated sessions can trigger the race condition; this does not fix the underlying flaw but shrinks the attack surface in multi-tenant environments. No additional vendor-documented workarounds are available.

Vendor StatusVendor

SUSE

Severity: Important
Product Status
SUSE Linux Enterprise High Performance Computing 15 SP7 SUSE Linux Enterprise Module for Server Applications 15 SP7 SUSE Linux Enterprise Server 15 SP7 SUSE Linux Enterprise Server for SAP Applications 15 SP7 Fixed
SUSE Linux Enterprise Server 15 SP6-LTSS Fixed
SUSE Linux Enterprise Server 16.0 SUSE Linux Enterprise Server for SAP applications 16.0 Fixed
SUSE Linux Enterprise Server for SAP Applications 15 SP6 Fixed
openSUSE Leap 16.0 Fixed

Share

EUVD-2026-60822 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy