Skip to main content
VulnerabilityPublished Updated

CVE-2026-85522: valkey-io valkey

Affects valkeySource GCVE Database

0
Compare
Authoritative record:CVE-2026-85522· Medium 6.9

Public exploit available · CVSS 6.9 Medium : upgrade to 9.0.4-0ubuntu0.2 as a priority.

Data as of 17 Nov 2026, 20:39 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 9.0.4-0ubuntu0.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Sep 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

Upgrade the Ubuntu valkey package to 9.0.4-0ubuntu0.2.

Affected software

ProductAffectedFixed in
Ubuntu 26.04 LTSvalkeypkg:deb/ubuntu/valkey?arch=source&distro=resoluteOther threatsAffected
  • <9.0.4-0ubuntu0.2
Fixed in
  • 9.0.4-0ubuntu0.2
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 detected in valkey-io valkey up to 9.5.4/9.1.0. Affected by this vulnerability is the function createSlotImportJob of the file src/cluster_migrateslots.c of the component Slot Migration. The manipulation of the argument job_name results in out-of-bounds read. The attack can be executed remotely. The exploit is now public and may be used. Upgrading to version 9.0.5 and 9.1.1 addresses this issue. The patch is identified as f4dc3ca09eb650c2fe14060090a41c524eca803f. Upgrading the affected component is advised.

References

Community reviews

Loading reviews…