Redict 7.3.5 is now available and includes security updates of moderate importance. Deployments which allow authenticated, untrusted users access to the Redict database are asked to upgrade urgently.

You may download the release on Codeberg, or update your official container images via registry.redict.io.

Redict 7.3.5 includes fixes for the following security vulnerabilities:

• CVE-2025-32023

No other changes are included in this release.

The SHA-256 checksum of the Redict 7.3.5 release tarball is 1528db77c3539190ebe1fe3963347e02ac8095aff75a19b3373cddcf3f920405.

Redict 7.3.4 is now available and includes minor security updates. You may download the release on Codeberg, or update your official container images via registry.redict.io.

Redict 7.3.4 includes fixes for the following security vulnerabilities:

• CVE-2025-48367

No other changes are included in this release.

The SHA-256 checksum of the Redict 7.3.4 release tarball is 6c7e60b8b10a46f6fce8ccaaf1d6bf9d0db796a4d6169422c34dedbf8a4cb680.

Redict 7.3.3 is now available and includes important security updates. You may download the release on Codeberg, or update your official container images via registry.redict.io.

Redict 7.3.3 includes fixes for the following security vulnerabilities:

• CVE-2025-21605

No other changes are included in this release.

The SHA-256 checksum of the Redict 7.3.3 release tarball is 5f96a35620f134ff8d3e91fe9b63ef2f45d343b12b94790ba61cdf2178516b26.

Redict 7.3.2 is now available and includes important security updates. You may download the release on Codeberg, or update your official container images via registry.redict.io.

Redict 7.3.2 includes fixes for the following security vulnerabilities:

• CVE-2024-46981
• CVE-2024-51741

No other changes are included in this release.

The SHA-256 checksum of the Redict 7.3.2 release tarball is c00ddb7d9eea879b3effc3dd7d1a8cff954fb472915ab9002ec56068c3af2a73.

Redict 7.3.1 is now available and includes important security updates. You may download the release on Codeberg, or update your official container images via registry.redict.io.

Redict 7.3.1 includes fixes for the following security vulnerabilities:

• CVE-2024-31449
• CVE-2024-31227
• CVE-2024-31228

No other changes are included in this release.

The SHA-256 checksum of the Redict 7.3.1 release tarball is 6dbe80d28503a9252048ab81856efcfec109cdf3f924e840411c30237cf8f634.

Please be advised that Redict version 7.3.1 is scheduled for release on October 1st and includes changes which address the following vulnerabilities (currently under embargo):

• CVE-2024-31449
• CVE-2024-31227
• CVE-2024-31228

Users are encouraged to upgrade their Redict installation urgently once the release is available on October 1st.

The Redict community is pleased to announce the release of Redict 7.3.0, the first stable version of our copyleft fork of Redis® OSS 7.2.4.¹ You can download the release on Codeberg, or download one of our official container images from registry.redict.io.

We have written comprehensive documentation detailing our compatibility with Redis® OSS 7.2.4, which also provides detailed documentation for various migration scenarios, such as for users of the official Redis® containers on Docker Hub, downstream package maintainers, and so on.

The initial release candidate for Redict’s first general release, 7.3.0-rc1, is now available for download and testing. You can find the release on Codeberg:

Redict 7.3.0-rc1

• Release notes
• Download .tar.gz
• Browse source code

Update: 7.3.0-rc2 is now available, with two minor changes from rc1:

Redict 7.3.0-rc2

• Release notes
• Download .tar.gz
• Browse source code

First time here? Redict is an independent fork of Redis®* OSS 7.2.4 licensed under the Lesser GNU General Public license (LGPL-3.0-only). Redict is not affiliated with Redis®. See the announcement for more details.

...

Like many of you, I was disappointed when I learned that Redis®¹ was changing to a non-free licensing model. This is a betrayal of the free software community, but perhaps not an entirely surprising one. Forks are likely to start appearing in the coming days, and today, I would like to offer Redict to you as a possible future home for your needs, and present its trade-offs as compared to the other forks you’re likely to be choosing from soon.