valkey-io valkey 9.1.0 Blocked-on-keys Subsystem src/blocked.c handleClientsBlockedOnKey use after free
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.0 | $0-$5k | 2.06+ |
Summary
A vulnerability was found in valkey-io valkey 9.1.0. It has been classified as problematic. The impacted element is the function handleClientsBlockedOnKey of the file src/blocked.c of the component Blocked-on-keys Subsystem. This manipulation causes use after free.
The identification of this vulnerability is CVE-2026-82631. It is possible to initiate the attack remotely. Furthermore, there is an exploit available.
It is suggested to install a patch to address this issue.
Details
A vulnerability has been found in valkey-io valkey 9.1.0 and classified as problematic. Affected by this vulnerability is the function handleClientsBlockedOnKey of the file src/blocked.c of the component Blocked-on-keys Subsystem. The manipulation with an unknown input leads to a use after free vulnerability. The CWE definition for the vulnerability is CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. As an impact it is known to affect availability.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-82631. The exploitation appears to be difficult. The attack can be launched remotely. Additional levels of successful authentication are needed for exploitation. Technical details and also a public exploit are known.
It is possible to download the exploit at github.com. It is declared as proof-of-concept.
Applying the patch b2fb0e13f5b4c8c2fb63dcfc2c37a067a0d6d20b is able to eliminate this problem. The bugfix is ready for download at github.com.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
Website
- Product: https://github.com/valkey-io/valkey/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 2.2VulDB Meta Temp Score: 2.0
VulDB Base Score: 2.2
VulDB Temp Score: 2.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Use after freeCWE: CWE-416 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔒
Patch: b2fb0e13f5b4c8c2fb63dcfc2c37a067a0d6d20b
Timeline
08/30/2026 Advisory disclosed08/30/2026 VulDB entry created
08/30/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 4198
Status: Confirmed
Confirmation: 🔒
CVE: CVE-2026-82631 (🔒)
GCVE (CVE): GCVE-0-2026-82631
GCVE (VulDB): GCVE-100-397129
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 08/30/2026 12:15Changes: 08/30/2026 12:15 (61)
Complete: 🔍
Submitter: VULL
Cache ID: 216::103
Submit
Accepted
- Submit #893793: Valkey Project Valkey 9.1.0 Heap Use After Free (by VULL)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.