CVE-2026-82631 json
valkey-io valkey Blocked-on-keys blocked.c handleClientsBlockedOnKey use after free
published 2mo ago modified 2mo ago also EUVD-2026-68393
- cvss
- 2.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 30%
- public exploits
- 0
- none known
Summary
A security flaw has been discovered in valkey-io valkey 9.1.0. The affected element is the function handleClientsBlockedOnKey of the file src/blocked.c of the component Blocked-on-keys Subsystem. The manipulation results in use after free. The attack may be performed from remote. A high complexity level is associated with this attack. The exploitability is described as difficult. The exploit has been released to the public and may be used for attacks. The patch is identified as b2fb0e13f5b4c8c2fb63dcfc2c37a067a0d6d20b. Applying a patch is advised to resolve this issue.
Patch / fix
- valkey Debian 13 8.1.1+dfsg1-3+deb13u3
- valkey Debian 14 9.1.2-1
debian advisories DEBIAN-CVE-2026-82631
- 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
red hat advisories RHSA-2026:61884
- github.com/valkey-io/valkey@b2fb0e1 commit
- github.com/valkey-io/valkey#4212 pull request
Is CVE-2026-82631 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor 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-82631 updated
valkey: Valkey: Use-after-free vulnerability in Blocked-on-keys subsystem
-
Red Hat Enterprise Linux 9 valkey, rhel9/valkey-8 Red Hat Enterprise Linux 10 valkey, rhel10/valkey-8affected: no fix available “Fix deferred”
-
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.hum1fixed: 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
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2mo ago
Exploit prediction
0.36% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/user-attachments/files/30111628/PoC.zip referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 2.1 | CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P |
| CNA | 3.1 | 2.2 | CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L/E:P/RL:O/RC:C |
| CNA | 3.0 | 2.2 | CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L/E:P/RL:O/RC:C |
| CNA | 2.0 | 1.7 | AV:N/AC:H/Au:M/C:N/I:N/A:P/E:POC/RL:OF/RC:C |
| CNA | 4.0 | 1.2 | CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| CNA | 3.1 | 2.2 | CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L |
| CNA | 2.0 | 1.7 | AV:N/AC:H/Au:M/C:N/I:N/A:P |
Affected products
- valkey-io valkey
Classification
References
-
github.com
/valkey-io/valkey/pull/4212
issue-tracking, patch
-
github.com
/valkey-io/valkey/commit/b2fb0e13f5b4c8c2fb63dcfc2c37a067a0d6d20b
patch
-
github.com
/user-attachments/files/30111628/PoC.zip
exploit
-
vuldb.com
/vuln/397129
vdb-entry, technical-description
-
vuldb.com
/vuln/397129/cti
signature, permissions-required
-
vuldb.com
/cve/CVE-2026-82631
third-party-advisory
-
vuldb.com
/submit/893793
third-party-advisory
-
github.com
/valkey-io/valkey/issues/4198
issue-tracking
-
github.com
/valkey-io/valkey/
product
Sources
- CVE List CVE-2026-82631
- NVD CVE-2026-82631
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.