Debian Package Tracker
Register | Log in
Subscribe

redict

Persistent key-value database with network interface (metapackage)

Choose email to subscribe with

general
  • source: redict (main)
  • version: 7.3.6+ds-3
  • maintainer: Debian Redict Maintainers (DMD)
  • uploaders: Maytham Alsudany [DMD]
  • arch: all any
  • std-ver: 4.7.4
  • VCS: Git (Browse, QA)
versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]
[pool directory]
  • old-bpo: 7.3.6+ds-2~bpo12+1
  • stable-bpo: 7.3.6+ds-2~bpo13+1
  • testing: 7.3.6+ds-3
  • unstable: 7.3.6+ds-3
versioned links
  • 7.3.6+ds-2~bpo12+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 7.3.6+ds-2~bpo13+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 7.3.6+ds-3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • redict
  • redict-sentinel
  • redict-server
  • redict-tools
action needed
The VCS repository is not up to date, push the missing commits. high
vcswatch reports that the current version of the package is not in its VCS.
Either you need to push your commits and/or your tags, or the information about the package's VCS are out of date. A common cause of the latter issue when using the Git VCS is not specifying the correct branch when the packaging is not in the default one (remote HEAD branch), which is usually "master" but can be modified in salsa.debian.org in the project's general settings with the "Default Branch" field). Alternatively the Vcs-Git field in debian/control can contain a "-b <branch-name>" suffix to indicate what branch is used for the Debian packaging.
Created: 2026-09-04 Last update: 2026-10-03 02:00
7 security issues in sid high

There are 7 open security issues in sid.

7 important issues:
  • CVE-2026-23479: Redis is an in-memory data structure store. In redis-server from 7.2.0 until 8.6.3, the unblock client flow does not handle an error return from `processCommandAndResetClient` when re-executing a blocked command. If a blocked client is evicted during this flow, an authenticated attacker can trigger a use-after-free that may lead to remote code execution. This has been patched in version 8.6.3.
  • CVE-2026-23631: Redis is an in-memory data structure store. In all versions of redis-server with Lua scripting, an authenticated attacker can exploit the master-replica synchronization mechanism to trigger a use-after-free on replicas where replica-read-only is disabled or can be disabled, which may lead to remote code execution. A workaround is to prevent users from executing Lua scripts or avoid using replicas where replica-read-only is disabled. This is patched in version 8.6.3.
  • CVE-2026-25243: Redis is an in-memory data structure store. In versions of redis-server up to 8.6.3, the RESTORE command does not properly validate serialized values. An authenticated attacker with permission to execute RESTORE can supply a crafted serialized payload that triggers invalid memory access and may lead to remote code execution. A workaround is to restrict access to the RESTORE command with ACL rules. This is patched in version 8.6.3.
  • CVE-2026-56684: Valkey is a distributed key-value database. Prior to 7.2.14, 8.0.10, 8.1.9, 9.0.5, and 9.1.1, Valkey's tlsProcessPendingData function iterates pending_list while an authenticated client can trigger CLIENT KILL, causing connTLSClose to delete the iterator's cached next node and producing a use-after-free that can crash the server or potentially allow remote code execution when TLS is enabled. This issue is fixed in versions 7.2.14, 8.0.10, 8.1.9, 9.0.5, and 9.1.1.
  • CVE-2026-63639: Valkey is a distributed key-value database. Prior to 7.2.14, 8.0.10, 8.1.9, 9.0.5, and 9.1.1, Valkey's RESTORE command accepts a malformed RDB stream payload that assigns one Pending Entry List NACK to multiple consumers during stream consumer-group deserialization, causing a use-after-free when one consumer is deleted while another still references the shared NACK and potentially allowing remote code execution. This issue is fixed in versions 7.2.14, 8.0.10, 8.1.9, 9.0.5, and 9.1.1.
  • CVE-2026-82631: A security flaw has been discovered in valkey-io valkey 9.1.0. The affected element is the function handleClientsBlockedOnKey of the file src/blocked.c of the component Blocked-on-keys Subsystem. The manipulation results in use after free. The attack may be performed from remote. A high complexity level is associated with this attack. The exploitability is described as difficult. The exploit has been released to the public and may be used for attacks. The patch is identified as b2fb0e13f5b4c8c2fb63dcfc2c37a067a0d6d20b. Applying a patch is advised to resolve this issue.
  • CVE-2026-82677: A vulnerability was determined in valkey-io valkey 9.1.0. Impacted is the function moduleTimerHandler of the file src/module.c of the component Module Timer Subsystem. This manipulation causes double free. The attack can be initiated remotely. The exploit has been publicly disclosed and may be utilized. Patch name: b349fe2821e3998534b1454c1b64a478daf8c6b7. To fix this issue, it is recommended to deploy a patch.
Created: 2026-09-30 Last update: 2026-09-30 07:31
7 security issues in forky high

There are 7 open security issues in forky.

7 important issues:
  • CVE-2026-23479: Redis is an in-memory data structure store. In redis-server from 7.2.0 until 8.6.3, the unblock client flow does not handle an error return from `processCommandAndResetClient` when re-executing a blocked command. If a blocked client is evicted during this flow, an authenticated attacker can trigger a use-after-free that may lead to remote code execution. This has been patched in version 8.6.3.
  • CVE-2026-23631: Redis is an in-memory data structure store. In all versions of redis-server with Lua scripting, an authenticated attacker can exploit the master-replica synchronization mechanism to trigger a use-after-free on replicas where replica-read-only is disabled or can be disabled, which may lead to remote code execution. A workaround is to prevent users from executing Lua scripts or avoid using replicas where replica-read-only is disabled. This is patched in version 8.6.3.
  • CVE-2026-25243: Redis is an in-memory data structure store. In versions of redis-server up to 8.6.3, the RESTORE command does not properly validate serialized values. An authenticated attacker with permission to execute RESTORE can supply a crafted serialized payload that triggers invalid memory access and may lead to remote code execution. A workaround is to restrict access to the RESTORE command with ACL rules. This is patched in version 8.6.3.
  • CVE-2026-56684: Valkey is a distributed key-value database. Prior to 7.2.14, 8.0.10, 8.1.9, 9.0.5, and 9.1.1, Valkey's tlsProcessPendingData function iterates pending_list while an authenticated client can trigger CLIENT KILL, causing connTLSClose to delete the iterator's cached next node and producing a use-after-free that can crash the server or potentially allow remote code execution when TLS is enabled. This issue is fixed in versions 7.2.14, 8.0.10, 8.1.9, 9.0.5, and 9.1.1.
  • CVE-2026-63639: Valkey is a distributed key-value database. Prior to 7.2.14, 8.0.10, 8.1.9, 9.0.5, and 9.1.1, Valkey's RESTORE command accepts a malformed RDB stream payload that assigns one Pending Entry List NACK to multiple consumers during stream consumer-group deserialization, causing a use-after-free when one consumer is deleted while another still references the shared NACK and potentially allowing remote code execution. This issue is fixed in versions 7.2.14, 8.0.10, 8.1.9, 9.0.5, and 9.1.1.
  • CVE-2026-82631: A security flaw has been discovered in valkey-io valkey 9.1.0. The affected element is the function handleClientsBlockedOnKey of the file src/blocked.c of the component Blocked-on-keys Subsystem. The manipulation results in use after free. The attack may be performed from remote. A high complexity level is associated with this attack. The exploitability is described as difficult. The exploit has been released to the public and may be used for attacks. The patch is identified as b2fb0e13f5b4c8c2fb63dcfc2c37a067a0d6d20b. Applying a patch is advised to resolve this issue.
  • CVE-2026-82677: A vulnerability was determined in valkey-io valkey 9.1.0. Impacted is the function moduleTimerHandler of the file src/module.c of the component Module Timer Subsystem. This manipulation causes double free. The attack can be initiated remotely. The exploit has been publicly disclosed and may be utilized. Patch name: b349fe2821e3998534b1454c1b64a478daf8c6b7. To fix this issue, it is recommended to deploy a patch.
Created: 2026-09-30 Last update: 2026-09-30 07:31
1 security issue in trixie high

There is 1 open security issue in trixie.

1 important issue:
  • CVE-2025-21605: Redis is an open source, in-memory database that persists on disk. In versions starting at 2.6 and prior to 7.4.3, An unauthenticated client can cause unlimited growth of output buffers, until the server runs out of memory or is killed. By default, the Redis configuration does not limit the output buffer of normal clients (see client-output-buffer-limit). Therefore, the output buffer can grow unlimitedly over time. As a result, the service is exhausted and the memory is unavailable. When password authentication is enabled on the Redis server, but no password is provided, the client can still cause the output buffer to grow from "NOAUTH" responses until the system will run out of memory. This issue has been patched in version 7.4.3. An additional workaround to mitigate this problem without patching the redis-server executable is to block access to prevent unauthenticated users from connecting to Redis. This can be done in different ways. Either using network access control tools like firewalls, iptables, security groups, etc, or enabling TLS and requiring users to authenticate using client side certificates.
Created: 2025-04-24 Last update: 2025-04-24 10:32
lintian reports 8 warnings normal
Lintian reports 8 warnings about this package. You should make the package lintian clean getting rid of them.
Created: 2026-09-05 Last update: 2026-09-05 01:32
debian/patches: 4 patches to forward upstream low

Among the 10 debian patches available in version 7.3.6+ds-3 of the package, we noticed the following issues:

  • 4 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.
Created: 2025-08-04 Last update: 2026-09-04 21:04
testing migrations
  • This package will soon be part of the auto-openssl transition. You might want to ensure that your package is ready for it. You can probably find supplementary information in the debian-release archives or in the corresponding release.debian.org bug.
news
[rss feed]
  • [2026-09-09] redict 7.3.6+ds-3 MIGRATED to testing (Debian testing watch)
  • [2026-09-04] Accepted redict 7.3.6+ds-3 (source) into unstable (Alex Myczko)
  • [2026-05-18] redict 7.3.6+ds-2 MIGRATED to testing (Debian testing watch)
  • [2026-05-10] Accepted redict 7.3.6+ds-2~bpo13+1 (source) into stable-backports (Maytham Alsudany)
  • [2026-05-10] Accepted redict 7.3.6+ds-2~bpo12+1 (source) into oldstable-backports (Maytham Alsudany)
  • [2026-05-08] Accepted redict 7.3.6+ds-2 (source) into unstable (Maytham Alsudany)
  • [2026-04-29] redict REMOVED from testing (Debian testing watch)
  • [2025-10-13] Accepted redict 7.3.6+ds-1~bpo13+1 (source amd64 all) into stable-backports (Debian FTP Masters) (signed by: Maytham Alsudany)
  • [2025-10-13] redict 7.3.6+ds-1 MIGRATED to testing (Debian testing watch)
  • [2025-10-11] Accepted redict 7.3.6+ds-1~bpo12+1 (source) into oldstable-backports (Maytham Alsudany)
  • [2025-10-11] Accepted redict 7.3.6+ds-1 (source) into unstable (Maytham Alsudany)
  • [2025-08-17] Accepted redict 7.3.5+ds-1~bpo12+1 (source amd64 all) into oldstable-backports (Debian FTP Masters) (signed by: Maytham Alsudany)
  • [2025-08-13] redict 7.3.5+ds-1 MIGRATED to testing (Debian testing watch)
  • [2025-08-03] Accepted redict 7.3.5+ds-1 (source) into unstable (Maytham Alsudany)
  • [2025-05-24] redict REMOVED from testing (Debian testing watch)
  • [2025-01-11] redict 7.3.2+ds-1 MIGRATED to testing (Debian testing watch)
  • [2025-01-09] Accepted redict 7.3.2+ds-1~bpo12+1 (source) into stable-backports (Maytham Alsudany)
  • [2025-01-08] Accepted redict 7.3.2+ds-1 (source) into unstable (Maytham Alsudany)
  • [2024-10-15] redict 7.3.1+ds-1 MIGRATED to testing (Debian testing watch)
  • [2024-10-13] Accepted redict 7.3.1+ds-1 (source) into unstable (Maytham Alsudany)
  • [2024-06-25] Accepted redict 7.3.0+ds-3~bpo12+1 (source amd64 all) into stable-backports (Debian FTP Masters) (signed by: Gürkan Myczko)
  • [2024-05-17] redict 7.3.0+ds-3 MIGRATED to testing (Debian testing watch)
  • [2024-05-17] redict 7.3.0+ds-3 MIGRATED to testing (Debian testing watch)
  • [2024-05-15] Accepted redict 7.3.0+ds-3 (source) into unstable (Maytham Alsudany) (signed by: Gürkan Myczko)
  • [2024-05-12] Accepted redict 7.3.0+ds-2 (source) into unstable (Maytham Alsudany) (signed by: Gürkan Myczko)
  • [2024-05-11] Accepted redict 7.3.0+ds-1 (source amd64 all) into unstable (Debian FTP Masters) (signed by: Gürkan Myczko)
bugs [bug history graph]
  • all: 2
  • RC: 0
  • I&N: 0
  • M&W: 2
  • F&P: 0
  • patch: 0
links
  • homepage
  • lintian (0, 8)
  • buildd: logs, reproducibility, cross
  • popcon
  • browse source code
  • other distros
  • security tracker
  • debian patches
  • debci
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 7.3.6+ds-2build1

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing