redis - Debian Package Tracker

general

source: redis (main)
version: 5:8.0.6-2
maintainer: Chris Lamb (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]

o-o-stable: 5:6.0.16-1+deb11u2
o-o-sec: 5:6.0.16-1+deb11u8
oldstable: 5:7.0.15-1~deb12u6
old-sec: 5:7.0.15-1~deb12u7
stable: 5:8.0.2-3+deb13u1
stable-sec: 5:8.0.2-3+deb13u2
testing: 5:8.0.6-1
unstable: 5:8.0.6-2
exp: 5:8.6.3-1

versioned links

5:6.0.16-1+deb11u2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
5:6.0.16-1+deb11u8: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
5:7.0.15-1~deb12u6: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
5:7.0.15-1~deb12u7: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
5:8.0.2-3+deb13u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
5:8.0.2-3+deb13u2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
5:8.0.6-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
5:8.0.6-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
5:8.4.0-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
5:8.6.3-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

redis
redis-sentinel
redis-server (6 bugs: 0, 6, 0, 0)
redis-tools

action needed

3 security issues in trixie high

There are 3 open security issues in trixie.

3 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.

Created: 2026-02-24 Last update: 2026-05-17 11:30

3 security issues in sid high

There are 3 open security issues in sid.

3 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.

Created: 2026-05-13 Last update: 2026-05-17 11:30

3 security issues in forky high

There are 3 open security issues in forky.

3 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.

Created: 2026-05-13 Last update: 2026-05-17 11:30

8 security issues in bullseye high

There are 8 open security issues in bullseye.

3 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.

5 ignored issues:

CVE-2021-31294: Redis before 6cbea7d allows a replica to cause an assertion failure in a primary server by sending a non-administrative command (specifically, a SET command). NOTE: this was fixed for Redis 6.2.x and 7.x in 2021. Versions before 6.2 were not intended to have safety guarantees related to this.
CVE-2022-24735: Redis is an in-memory database that persists on disk. By exploiting weaknesses in the Lua script execution environment, an attacker with access to Redis prior to version 7.0.0 or 6.2.7 can inject Lua code that will execute with the (potentially higher) privileges of another Redis user. The Lua script execution environment in Redis provides some measures that prevent a script from creating side effects that persist and can affect the execution of the same, or different script, at a later time. Several weaknesses of these measures have been publicly known for a long time, but they had no security impact as the Redis security model did not endorse the concept of users or privileges. With the introduction of ACLs in Redis 6.0, these weaknesses can be exploited by a less privileged users to inject Lua code that will execute at a later time, when a privileged user executes a Lua script. The problem is fixed in Redis versions 7.0.0 and 6.2.7. An additional workaround to mitigate this problem without patching the redis-server executable, if Lua scripting is not being used, is to block access to `SCRIPT LOAD` and `EVAL` commands using ACL rules.
CVE-2022-24736: Redis is an in-memory database that persists on disk. Prior to versions 6.2.7 and 7.0.0, an attacker attempting to load a specially crafted Lua script can cause NULL pointer dereference which will result with a crash of the redis-server process. The problem is fixed in Redis versions 7.0.0 and 6.2.7. An additional workaround to mitigate this problem without patching the redis-server executable, if Lua scripting is not being used, is to block access to `SCRIPT LOAD` and `EVAL` commands using ACL rules.
CVE-2024-31449: Redis is an open source, in-memory database that persists on disk. An authenticated user may use a specially crafted Lua script to trigger a stack buffer overflow in the bit library, which may potentially lead to remote code execution. The problem exists in all versions of Redis with Lua scripting. This problem has been fixed in Redis versions 6.2.16, 7.2.6, and 7.4.1. Users are advised to upgrade. There are no known workarounds for this vulnerability.
CVE-2025-46818: Redis is an open source, in-memory database that persists on disk. Versions 8.2.1 and below allow an authenticated user to use a specially crafted Lua script to manipulate different LUA objects and potentially run their own code in the context of another user. The problem exists in all versions of Redis with LUA scripting. This issue is fixed in version 8.2.2. A workaround to mitigate the problem without patching the redis-server executable is to prevent users from executing LUA scripts. This can be done using ACL to block a script by restricting both the EVAL and FUNCTION command families.

Created: 2026-05-13 Last update: 2026-05-17 11:30

3 security issues in bookworm high

There are 3 open security issues in bookworm.

3 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.

Created: 2026-02-24 Last update: 2026-05-17 11:30

Problems while searching for a new upstream version high

uscan had problems while searching for a new upstream version:

In debian/watch no matching files for watch source
  https://github.com/redis/redis/tags

Created: 2026-05-08 Last update: 2026-05-17 11:30

Fails to build during reproducibility testing normal

A package building reproducibly enables third parties to verify that the source matches the distributed binaries. It has been identified that this source package produced different results, failed to build or had other issues in a test environment. Please read about how to improve the situation!

Created: 2026-05-04 Last update: 2026-05-17 15:04

1 new commit since last upload, is it time to release? normal

vcswatch reports that this package seems to have new commits in its VCS but has not yet updated debian/changelog. You should consider updating the Debian changelog and uploading this new version into the archive.

Here are the relevant commit logs:

commit 2e75ae1b77107c1dcdf47da2092a32eeb36d868f
Author: Chris Lamb <lamby@debian.org>
Date:   Wed May 13 13:46:29 2026 -0700

    Also specify CPPFLAGS in tests/modules/Makefile and deps/fast_float/Makefile.

Created: 2026-05-13 Last update: 2026-05-13 22:33

3 open merge requests in Salsa normal

There are 3 open merge requests for this package on Salsa. You should consider reviewing and/or merging these merge requests.

Created: 2025-08-19 Last update: 2026-05-11 18:30

lintian reports 1 warning normal

Lintian reports 1 warning about this package. You should make the package lintian clean getting rid of them.

Created: 2026-04-11 Last update: 2026-04-11 03:01

debian/patches: 4 patches to forward upstream low

Among the 8 debian patches available in version 5:8.0.6-2 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: 2023-02-26 Last update: 2026-05-14 09:03

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.
excuses:
- Migration status for redis (5:8.0.6-1 to 5:8.0.6-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- ∙ ∙ Autopkgtest for cachelib/0.13.0-2: amd64: Pass, arm64: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for debusine/0.14.7: amd64: Pass, arm64: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
- ∙ ∙ Autopkgtest for django-q/1.9.0-1: amd64: Pass, arm64: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for django-redis/5.4.0-1: amd64: Pass, arm64: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for golang-github-go-redis-redis/6.15.0-3: amd64: Pass, arm64: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for golang-github-gomodule-redigo/1:1.9.3-1: amd64: Pass, arm64: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for golang-github-stvp-tempredis/0.0~git20231107.8a695b6-2: amd64: Pass, arm64: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for guile-redis/2.2.0-2: amd64: Pass, arm64: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for libanyevent-redis-perl/0.24-4: amd64: Pass, arm64: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for libredis-fast-perl/0.37+dfsg-1: amd64: Pass, arm64: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for libredis-perl/2:2.000-1: amd64: Pass, arm64: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for libtest-redisserver-perl/0.24-1: amd64: Pass, arm64: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for logbook/1.7.0-1.0: amd64: Pass, arm64: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for mirrorbits/0.6.1-1: i386: Pass ♻, riscv64: Pass ♻
- ∙ ∙ Autopkgtest for mirrorbits/0.6.1-2: amd64: Pass, arm64: Pass, loong64: Test triggered, ppc64el: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for proftpd-dfsg/1.3.9a~dfsg-1: amd64: Pass, arm64: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for pyrate-limiter/4.1.0-1: amd64: Pass, arm64: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Failed (not a regression) ♻ (reference ♻), s390x: Pass
- ∙ ∙ Autopkgtest for python-channels-redis/4.3.0-1: amd64: Pass, arm64: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-ratelimit/4.1.0-2: amd64: Pass, arm64: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-django-structlog/10.0.0-2: amd64: Pass, arm64: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-fakeredis/2.29.0-6: amd64: Pass, arm64: Pass, i386: Pass, loong64: Test triggered, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-redis/6.4.0-1: amd64: Pass, arm64: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python-rq/2.8-2: amd64: Pass, arm64: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: No tests, superficial or marked flaky ♻, s390x: Pass
- ∙ ∙ Autopkgtest for rails/2:7.2.3.1+dfsg-1: amd64: Pass, arm64: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for redis/5:8.0.6-2: amd64: Pass, arm64: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for ruby-database-cleaner/1.7.0-2: amd64: Pass, arm64: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for ruby-redis/5.4.1-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, loong64: Test triggered, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ Autopkgtest for ruby-redis-namespace: amd64: Test triggered (failure will be ignored), arm64: Test triggered (failure will be ignored), i386: Test triggered (failure will be ignored), loong64: Test triggered (failure will be ignored), ppc64el: Test triggered (failure will be ignored), riscv64: Test triggered (failure will be ignored), s390x: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for ruby-redis-store/1.11.0-1: amd64: Pass, arm64: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for ruby-sidekiq/7.3.2+dfsg-1: amd64: Pass, arm64: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for webdis/0.1.22+ds-1: amd64: Pass, arm64: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Too young, only 3 of 5 days old
- Additional info (not blocking):
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/r/redis.html
- ∙ ∙ Reproduced on amd64 - info
- ∙ ∙ Reproduced on arm64 - info
- ∙ ∙ Reproduced on armhf - info
- ∙ ∙ Reproduced on i386 - info
- Not considered

news

[rss feed]

[2026-05-17] Accepted redis 5:7.0.15-1~deb12u7 (source) into oldstable-proposed-updates (Debian FTP Masters) (signed by: Aron Xu)
[2026-05-17] Accepted redis 5:8.0.2-3+deb13u2 (source) into stable-security (Debian FTP Masters) (signed by: Aron Xu)
[2026-05-17] Accepted redis 5:7.0.15-1~deb12u7 (source) into oldstable-security (Debian FTP Masters) (signed by: Aron Xu)
[2026-05-13] Accepted redis 5:8.6.3-1 (source) into experimental (Chris Lamb)
[2026-05-13] Accepted redis 5:8.0.6-2 (source) into unstable (Chris Lamb)
[2026-04-15] redis 5:8.0.6-1 MIGRATED to testing (Debian testing watch)
[2026-04-10] Accepted redis 5:8.0.6-1 (source) into unstable (Chris Lamb)
[2026-03-31] Accepted redis 5:8.6.2-1 (source) into experimental (Chris Lamb)
[2026-03-11] Accepted redis 5:8.6.1-1 (source) into experimental (Chris Lamb)
[2026-01-14] Accepted redis 5:8.4.0-1 (source) into experimental (Chris Lamb)
[2025-11-06] redis 5:8.0.5-1 MIGRATED to testing (Debian testing watch)
[2025-11-03] Accepted redis 5:8.0.5-1 (source) into unstable (Chris Lamb)
[2025-10-19] Accepted redis 5:7.0.15-1~deb12u6 (source) into oldstable-proposed-updates (Debian FTP Masters) (signed by: Moritz Mühlenhoff)
[2025-10-13] Accepted redis 5:8.0.2-3+deb13u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Moritz Mühlenhoff)
[2025-10-09] Accepted redis 5:6.0.16-1+deb11u8 (source) into oldoldstable-security (Chris Lamb)
[2025-10-08] Accepted redis 5:7.0.15-1~deb12u6 (source) into oldstable-security (Debian FTP Masters) (signed by: Moritz Mühlenhoff)
[2025-10-08] Accepted redis 5:8.0.2-3+deb13u1 (source) into stable-security (Debian FTP Masters) (signed by: Moritz Mühlenhoff)
[2025-10-08] redis 5:8.0.4-1 MIGRATED to testing (Debian testing watch)
[2025-10-04] Accepted redis 5:8.0.4-1 (source) into unstable (Chris Lamb)
[2025-08-02] Accepted redis 5:7.0.15-1~deb12u5 (source amd64 all) into proposed-updates (Debian FTP Masters) (signed by: Chris Lamb)
[2025-07-31] Accepted redis 5:7.0.15-1~deb12u5 (source amd64 all) into stable-security (Debian FTP Masters) (signed by: Chris Lamb)
[2025-07-23] redis 5:8.0.2-3 MIGRATED to testing (Debian testing watch)
[2025-07-17] Accepted redis 5:8.0.2-3 (source) into unstable (Chris Lamb)
[2025-07-12] Accepted redis 5:6.0.16-1+deb11u7 (source) into oldstable-security (Chris Lamb)
[2025-07-12] Accepted redis 5:8.0.2-2 (source) into unstable (Chris Lamb)
[2025-06-06] redis 5:8.0.0-2 MIGRATED to testing (Debian testing watch)
[2025-05-13] Accepted redis 5:8.0.0-2 (source) into unstable (Chris Lamb)
[2025-05-12] Accepted redis 5:8.0.0-1 (source) into experimental (Chris Lamb)
[2025-05-11] Accepted redis 5:6.0.16-1+deb11u6 (source) into oldstable-security (Adrian Bunk)
[2025-05-10] Accepted redis 5:7.0.15-1~deb12u4 (source) into proposed-updates (Debian FTP Masters) (signed by: Adrian Bunk)

bugs [bug history graph]

all: 8
RC: 1
I&N: 7
M&W: 0
F&P: 0
patch: 0

links

homepage
lintian (0, 1)
buildd: logs, exp, reproducibility, cross
popcon
browse source code
other distros
security tracker
debian patches
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 5:8.0.5-1
23 bugs