Skip to content
Fencer Intel
high 7.5

CVE-2026-56684 json

Valkey: TLS pending-data processing use-after-free may allow remote code execution

published 3mo ago modified 20d ago also BIT-valkey-2026-56684 , EUVD-2026-60822 , GHSA-53mc-f3m3-99vh

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 44%
public exploits
0
none known

Summary

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.

Patch / fix

  • bitnami valkey 7.2.14, 8.0.10, 8.1.9, 9.0.5, 9.1.1
  • valkey-io valkey 7.2.14, 8.0.10, 8.1.9, 9.0.5, 9.1.1
  • valkey Debian 13 8.1.1+dfsg1-3+deb13u3
  • valkey Debian 14 9.1.1-1

debian advisories DEBIAN-CVE-2026-56684

  • valkey Ubuntu 26.04 LTS 9.0.4-0ubuntu0.2
  • valkey Ubuntu Pro 24.04 LTS 7.2.13+dfsg1-0ubuntu0.1+esm1

ubuntu advisories UBUNTU-CVE-2026-56684

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • valkey hummingbird 1 9.0.6-0.1.hum1
  • valkey-rdma hummingbird 1 9.0.6-0.1.hum1
  • valkey-compat-redis hummingbird 1 9.0.6-0.1.hum1
  • valkey RHEL 9 8.0.10-1.el9_8
  • valkey RHEL 10.2 8.0.11-1.el10_2
  • valkey enterprise linux eus 10.0 8.0.11-1.el10_0

red hat advisories RHSA-2026:68601RHSA-2026:61884RHSA-2026:64807RHSA-2026:64796

  • valkey SLE Module for Server Applications 15 SP7 8.0.10-150700.3.20.1
  • valkey SLES for SAP 15 SP6, SLES 15 SP6-LTSS 8.0.10-150600.13.28.1

suse advisories SUSE-SU-2026:3483-1SUSE-SU-2026:3427-1

  • valkey openSUSE Leap 16.0 8.0.10-160000.1.1
  • valkey openSUSE Tumbleweed 9.1.1-1.1

opensuse advisories openSUSE-SU-2026:21485-1openSUSE-SU-2026:11381-1

  • valkey AlmaLinux 10 8.0.11-1.el10_2
  • valkey AlmaLinux 9 8.0.10-1.el9_8

almalinux advisories ALSA-2026:64796ALSA-2026:64807

  • valkey Rocky Linux 10 8.0.11-1.el10_2
  • valkey Rocky Linux 9 8.0.10-1.el9_8

rocky linux advisories RLSA-2026:64796RLSA-2026:64807

  • valkey Alpine 3.21 7.2.15-r0
  • valkey Alpine 3.22 8.1.11-r0
  • valkey Alpine 3.24, Alpine 3.23 9.0.7-r0

alpine advisories ALPINE-CVE-2026-56684

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • valkey Azure Linux 3.0 8.0.10-1

azure linux advisories AZL-96888

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Is CVE-2026-56684 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-56684 updated cvss 7.5

valkey: Valkey: Remote code execution via TLS pending-data processing use-after-free

  • Red Hat Enterprise Linux AppStream (v. 9) valkey 8.0.10-1.el9_8
    fixed: vendor fix RHSA-2026:64807
  • Red Hat Enterprise Linux AppStream (v. 10) valkey 8.0.11-1.el10_2
    fixed: vendor fix RHSA-2026:64796
  • Red Hat Enterprise Linux AppStream EUS (v. 10.0) valkey 8.0.11-1.el10_0
    fixed: vendor fix RHSA-2026:68601
  • Red Hat Hardened Images valkey 9.0.6-0.1.hum1, valkey-rdma 9.0.6-0.1.hum1, valkey-compat-redis 9.0.6-0.1.hum1
    fixed: vendor fix RHSA-2026:61884

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2mo ago

Exploit prediction

0.52% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
OSV 3.1 7.5 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
bitnami valkey
<7.2.14
>=8.0.0, <8.0.10
>=8.1.0, <8.1.9
>=9.0.0, <9.0.5
>=9.1.0, <9.1.1
7.2.14
8.0.10
8.1.9
9.0.5
9.1.1

Affected products

  • valkey-io valkey

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of valkey-io/valkey published their own advisory on GitHub. Reviewed sources take precedence over it.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.