Valkey Lifecycle policy

Valkey is tracked by BlackTree as a database platform or data-management product. Its lifecycle page separates release identity, maintenance and security boundaries using the publisher's registered source.

Evidence status

This record passed BlackTree's automatic primary-source checks with a confidence score of 82. It is returned for operational research without requiring routine manual approval. Confirm edition and deployment applicability before acting.

This discovery does not establish a product-specific support or retirement date. A missing date does not mean support continues.

Product overview

Main capabilities

Persistent data storage
Application data querying and management
Backup, security and operational administration

Typical use

Used as an application data store, analytical platform or managed data service.

Deployment

Operated on servers, virtual machines, containers or a vendor-managed cloud service.

This category-level context is generated from the registered product identity. Confirm exact product capabilities on the publisher's page .

Collected lifecycle data

Product	Valkey
Release	Lifecycle policy
Start or release	Not extracted
Lifecycle boundary	Continuous or not dated in the source
Date precision	Unknown

Known exploited vulnerabilities

Catalogue updated 1 Oct 2026

These are product-family matches in the CISA Known Exploited Vulnerabilities catalogue. Confirm the affected product version in the vendor advisory.

No CISA known-exploited entries currently match this mapped product family.

This does not mean the product has no vulnerabilities.

Package vulnerability advisories

Checked 29 Sep 2026

OSV advisories are matched through the registered package URL. A package-family match does not prove that the installed release is affected. Check the affected and fixed versions before remediation.

No package advisories have been linked for this product identity.

This is not evidence that the product has no vulnerabilities.

Source evidence

PRIMARYManual

Valkey official lifecycle source

Upgrading from a previous minor version should be safe, and will not introduce incompatibilities between servers in the cluster when default server configurations are used. | NOTE: Minor releases may include new commands and data types that can introduce incompatibility between servers in the cluster, but users need to opt-in to these features to cause this type of incompatibility. For this reason, it is not recommended to run a Valkey cluster with servers running on different minor versions. Users should avoid new features until all servers in the cluster have been upgraded. | Commands may also be marked as deprecated in minor versions. Deprecated commands are not removed, instead a replacement command or an alternative to using the command will be defined in the same minor version. | Major versions | Major versions are released with significant functionality that may break backwards compatibility or alter key performance characteristics. Examples of significant functionality includes altering the behavior of an existing command, removing previously deprecated commands, changing the default value of configs, and significant refactoring for performance improvements.

Publisher identity used by product-specific official-source collectors.

First collected 12 Sep 2026 · Last collected 27 Sep 2026 · Review state accepted

Open official vendor source