On this page (7 sections)
On October 27, 2026, Debian published DSA-6586-1, a security update for Valkey, the in-memory key-value database. It covers seven CVEs. Debian says the issues could cause denial of service and, in some cases, potentially allow arbitrary code execution.
If you run Valkey on Debian 13 (trixie), for example as a cache, session store or queue behind a web application, you should plan to upgrade. The advisory is short, so this article also covers how to check your exposure and what to watch afterwards.
What Debian announced
The Debian Security Team describes the update as fixing several vulnerabilities discovered in Valkey. The advisory lists seven CVE identifiers and three Debian bug numbers (1144956, 1144957 and 1146641). For the stable distribution, trixie, the fixes are in package version 8.1.1+dfsg1-3+deb13u3, and Debian recommends upgrading your valkey packages.
The advisory does not describe each flaw individually, and it gives no CVSS scores, affected version ranges beyond the trixie package, or attack conditions. Per-CVE detail is available through the Debian security tracker for valkey, which the advisory points to.
What the impact wording means
Debian groups the impact into two classes. Denial of service means a crafted request or condition can make the Valkey server crash, hang or exhaust resources, so applications that depend on it for caching or sessions slow down or fail. Arbitrary code execution is the more serious class: it means an attacker might run their own code on the host with the privileges of the Valkey process. Debian says this applies only to some of the issues and uses the word potentially, so treat it as a possibility rather than a confirmed attack path for every CVE.
Which of the seven CVEs falls into which class is not stated in the advisory, so the safe assumption is to treat the whole set as one upgrade.
Who is realistically exposed
- Servers on Debian 13 (trixie) with the valkey package installed from Debian's repositories.
- Web applications, stores and CMS sites that use Valkey for object caching, sessions, rate limiting or job queues.
- Hosts where Valkey listens on a network interface rather than only on localhost. A reachable instance gives an attacker more opportunity than one bound locally, although the advisory does not say whether the flaws need network access or authentication.
- Container images or other distributions that bundle Valkey. The advisory covers only the Debian package, so check your other vendors separately.
Debian's advisory names only trixie as the fixed stable release. If you run an older Debian release or a different distribution, check the security tracker and your vendor's notices rather than assuming you are unaffected or covered.
How to check your exposure
These commands list the installed valkey package and its version on Debian. You are looking for a version at or above 8.1.1+dfsg1-3+deb13u3 on trixie.
dpkg -l | grep valkey
apt-cache policy valkeyThis read-only check shows whether the Valkey process is running and which addresses it listens on. Look for a listener on 0.0.0.0 or a public address, which means it is reachable beyond the local machine. Valkey's default port is 6379, but your configuration may differ.
ss -tlnp | grep -E 'valkey|6379'What to do now
- Find every Debian host that runs valkey, including cache and queue servers that are easy to forget.
- Run the version check above and note any host below 8.1.1+dfsg1-3+deb13u3 on trixie.
- Take a snapshot or confirm your backups, and note whether the instance holds data you cannot rebuild.
- Upgrade the valkey package using the commands below during a maintenance window.
- Confirm the service is running after the upgrade and that your application reconnects normally.
- Check that Valkey is bound only to the interfaces it needs, and that a firewall blocks its port from the internet.
- Review other vendors and container images that ship Valkey and apply their updates when available.
These commands refresh the package index and upgrade only the valkey packages on Debian. Afterwards, the version check above should show the fixed version.
apt update
apt install --only-upgrade valkeyIf the package name differs on your system, use the output of the dpkg command above to see which valkey packages are installed and upgrade those.
Detection and monitoring afterwards
The advisory does not describe indicators of compromise, so there is no specific signature to hunt for. General hygiene still helps. Watch for unexpected Valkey restarts or crashes in your service logs, since denial of service is a named impact. Look for new or unfamiliar processes and outbound connections from the Valkey host, and for unexpected connections to its port from addresses that are not your application servers.
Keep an eye on the Debian security tracker for updates to individual CVEs, such as severity or exploitation notes added later. For broader hygiene on the web-facing side of the stack, see our guide to small business website security, and consider Webforta Monitor for uptime, certificate and DNS change alerts on your public sites. Uptime monitoring can help you notice an outage if a cache backend becomes unstable, though it does not tell you whether a backend is vulnerable.
If you manage the same Debian servers, other recent Debian advisories we covered may also apply to you, such as DSA-6587-1 for PowerDNS and DSA-6589-1 for php-mongodb.
Timeline
| Date | Event |
|---|---|
| October 27, 2026 | Debian publishes DSA-6586-1 with fixed valkey version 8.1.1+dfsg1-3+deb13u3 for trixie |
The advisory does not give discovery dates, disclosure timelines or details of who reported the flaws, so we do not list any.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
