Skip to main content
VulnerabilityPublished Updated

CVE-2026-82677: valkey-io valkey

Affects valkeySource GCVE Database

0
Compare
Authoritative record:CVE-2026-82677· Medium 4.8

Public exploit available · CVSS 4.8 Medium.

Data as of 17 Nov 2026, 20:39 UTC

CVSS 4.0 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Ubuntu 26.10valkeypkg:deb/ubuntu/valkey?arch=source&distro=stonkingOther threatsAffected
  • 9.0.3-0ubuntu2 – 9.1.2-0ubuntu1
4 affected builds
Fixed in–
Ubuntu 26.04 LTSvalkeypkg:deb/ubuntu/valkey?arch=source&distro=resoluteOther threatsAffected
  • 8.1.3+dfsg1-0ubuntu2 – 9.0.6-0ubuntu0.1
8 affected builds
Fixed in–
Ubuntu 24.04 LTSvalkeypkg:deb/ubuntu/valkey?arch=source&distro=nobleOther threatsAffected
  • 7.2.5+dfsg1-2ubuntu4~24.04.1 – 7.2.14+dfsg1-0ubuntu0.1
12 affected builds
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

A vulnerability was determined in valkey-io valkey 9.1.0. Impacted is the function moduleTimerHandler of the file src/module.c of the component Module Timer Subsystem. This manipulation causes double free. The attack can be initiated remotely. The exploit has been publicly disclosed and may be utilized. Patch name: b349fe2821e3998534b1454c1b64a478daf8c6b7. To fix this issue, it is recommended to deploy a patch.

References

Community reviews

Loading reviews…