# CVE-2026-85522: valkey-io valkey Slot Migration cluster_migrateslots.c createSlotImportJob out-of-bounds

> Remote attackers can trigger an out-of-bounds read in Valkey's slot migration feature, potentially causing crashes or leaking memory.

- **Severity:** Medium 6.9 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Sep 2026
- **Updated:** 4 Sep 2026
- **Also known as:** BELL-CVE-2026-85522, DEBIAN-CVE-2026-85522, GHSA-cmxq-3354-mw5w, UBUNTU-CVE-2026-85522

## What is CVE-2026-85522?

CVE-2026-85522 is a medium-severity memory corruption vulnerability in valkey-io valkey, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-125 (Out-of-bounds Read), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2026-85522?


## How do I fix CVE-2026-85522?

Upgrade to a fixed version.

## Is CVE-2026-85522 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85522 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-85522 and fix it if it is affected.

What it is: CVE-2026-85522 is a medium-severity memory corruption vulnerability in valkey-io valkey, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85522 exists.

Affected product: valkey-io valkey. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-85522/ (Markdown: https://insights.sbomify.com/CVE-2026-85522/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-85522
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-85522
- OSV: https://osv.dev/vulnerability/CVE-2026-85522

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-85522/
Summaries are generated and may contain mistakes; the official description above is the record.