{"id":"CVE-2025-21605","aliases":["ALPINE-CVE-2025-21605","ALSA-2025:7429","ALSA-2025:7438","ALSA-2025:7509","ALSA-2025:7686","AZL-60939","BELL-CVE-2025-21605","BIT-keydb-2025-21605","BIT-redis-2025-21605","BIT-valkey-2025-21605","CLSA-2025-1750785864","CLSA-2026-1788372462","DEBIAN-CVE-2025-21605","DLA-4162-1","EUVD-2025-12407","GHSA-r67f-p999-2gff","MGASA-2025-0171","OESA-2025-1474","OESA-2025-2837","OESA-2025-2838","OESA-2025-2839","OESA-2025-2840","OESA-2025-2841","OESA-2025-2862","RHSA-2025:4441","RHSA-2025:4561","RHSA-2025:4577","RHSA-2025:4607","RHSA-2025:4788","RHSA-2025:4789","RHSA-2025:7429","RHSA-2025:7438","RHSA-2025:7509","RHSA-2025:7538","RHSA-2025:7630","RHSA-2025:7686","RLSA-2025:7429","RLSA-2025:7438","RLSA-2025:7509","RLSA-2025:7686","SUSE-SU-2025:01942-1","SUSE-SU-2025:02010-1","SUSE-SU-2025:1419-1","SUSE-SU-2025:1420-1","SUSE-SU-2025:1432-1","SUSE-SU-2025:1433-1","SUSE-SU-2025:1566-1","UBUNTU-CVE-2025-21605","openSUSE-SU-2025:15035-1","openSUSE-SU-2025:15293-1"],"status":"published","title":"Redis DoS Vulnerability due to unlimited growth of output buffers abused by unauthenticated client","description":"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.","severity":{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-11","score":0.00872,"percentile":0.59311,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-770"],"published":"2025-04-23T15:38:11Z","modified":"2026-11-09T12:49:26Z","fixes":[{"ecosystem":"Alpine:v3.20","package":"redict","fixed_in":["7.3.3-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.21","package":"redict","fixed_in":["7.3.3-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.22","package":"redict","fixed_in":["7.3.3-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.23","package":"redict","fixed_in":["7.3.3-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.24","package":"redict","fixed_in":["7.3.3-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.15","package":"redis","fixed_in":["6.2.18-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.18","package":"redis","fixed_in":["7.0.15-r3"],"sources":["osv"]},{"ecosystem":"Alpine:v3.19","package":"redis","fixed_in":["7.2.8-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.20","package":"redis","fixed_in":["7.2.8-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.21","package":"redis","fixed_in":["7.2.8-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.22","package":"redis","fixed_in":["8.0.0-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.23","package":"redis","fixed_in":["8.0.0-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.24","package":"redis","fixed_in":["8.0.0-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.20","package":"valkey","fixed_in":["7.2.9-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.21","package":"valkey","fixed_in":["7.2.9-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.22","package":"valkey","fixed_in":["7.2.9-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.23","package":"valkey","fixed_in":["7.2.9-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.24","package":"valkey","fixed_in":["7.2.9-r0"],"sources":["osv"]},{"ecosystem":"AlmaLinux:9","package":"redis","fixed_in":["7.2.8-1.module_el9.6.0+168+b8d8e900","6.2.18-1.el9_6"],"sources":["osv"]},{"ecosystem":"AlmaLinux:9","package":"redis-devel","fixed_in":["7.2.8-1.module_el9.6.0+168+b8d8e900","6.2.18-1.el9_6"],"sources":["osv"]},{"ecosystem":"AlmaLinux:9","package":"redis-doc","fixed_in":["7.2.8-1.module_el9.6.0+168+b8d8e900","6.2.18-1.el9_6"],"sources":["osv"]},{"ecosystem":"AlmaLinux:10","package":"valkey","fixed_in":["8.0.3-1.el10_0"],"sources":["osv"]},{"ecosystem":"AlmaLinux:10","package":"valkey-devel","fixed_in":["8.0.3-1.el10_0"],"sources":["osv"]},{"ecosystem":"AlmaLinux:8","package":"redis","fixed_in":["6.2.18-1.module_el8.10.0+3994+c2cc5395"],"sources":["osv"]},{"ecosystem":"AlmaLinux:8","package":"redis-devel","fixed_in":["6.2.18-1.module_el8.10.0+3994+c2cc5395"],"sources":["osv"]},{"ecosystem":"AlmaLinux:8","package":"redis-doc","fixed_in":["6.2.18-1.module_el8.10.0+3994+c2cc5395"],"sources":["osv"]},{"ecosystem":"Azure Linux:3","package":"valkey","fixed_in":["8.0.3-1"],"sources":["osv"]},{"ecosystem":"Alpaquita:23","package":"redis","fixed_in":["7.0.15-r3"],"sources":["osv"]},{"ecosystem":"Alpaquita:stream","package":"redis","fixed_in":["8.0.0-r0"],"sources":["osv"]},{"ecosystem":"Bitnami","package":"keydb","fixed_in":["6.2.18","7.2.8","7.4.3"],"sources":["osv"]},{"ecosystem":"Bitnami","package":"redis","fixed_in":["6.2.18","7.2.8","7.4.3"],"sources":["osv"]},{"ecosystem":"Bitnami","package":"valkey","fixed_in":["7.2.9","8.0.3","8.1.1"],"sources":["osv"]},{"ecosystem":"TuxCare:AlmaLinux:9.2","package":"redis","fixed_in":["6.2.7-1.el9.tuxcare.els1"],"sources":["osv"]},{"ecosystem":"TuxCare:AlmaLinux:9.2","package":"redis-devel","fixed_in":["6.2.7-1.el9.tuxcare.els1"],"sources":["osv"]},{"ecosystem":"TuxCare:AlmaLinux:9.2","package":"redis-doc","fixed_in":["6.2.7-1.el9.tuxcare.els1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"redict","fixed_in":["7.3.5+ds-1"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"redis","fixed_in":["5:7.0.15-1~deb12u4"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"redis","fixed_in":["5:7.0.15-3.1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"redis","fixed_in":["5:7.0.15-3.1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"valkey","fixed_in":["8.1.1+dfsg1-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"valkey","fixed_in":["8.1.1+dfsg1-1"],"sources":["osv"]},{"ecosystem":"Debian:11","package":"redis","fixed_in":["5:6.0.16-1+deb11u6"],"sources":["osv"]},{"ecosystem":"Mageia:9","package":"redis","fixed_in":["7.0.14-1.3.mga9"],"sources":["osv"]},{"ecosystem":"openEuler:20.03-LTS-SP4","package":"redis","fixed_in":["7.2.8-1.oe2003sp4"],"sources":["osv"]},{"ecosystem":"openEuler:22.03-LTS-SP3","package":"redis","fixed_in":["7.2.8-1.oe2203sp3"],"sources":["osv"]},{"ecosystem":"openEuler:22.03-LTS-SP4","package":"redis","fixed_in":["7.2.8-1.oe2203sp4"],"sources":["osv"]},{"ecosystem":"openEuler:24.03-LTS","package":"redis","fixed_in":["7.2.8-1.oe2403sp1"],"sources":["osv"]},{"ecosystem":"openEuler:24.03-LTS-SP1","package":"redis","fixed_in":["7.2.8-1.oe2403sp1"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_aus:8.4::appstream","package":"redis","fixed_in":["0:6.0.9-5.module+el8.4.0+23067+0d16e377.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_aus:8.4::appstream","package":"redis-debuginfo","fixed_in":["0:6.0.9-5.module+el8.4.0+23067+0d16e377.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_aus:8.4::appstream","package":"redis-debugsource","fixed_in":["0:6.0.9-5.module+el8.4.0+23067+0d16e377.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_aus:8.4::appstream","package":"redis-devel","fixed_in":["0:6.0.9-5.module+el8.4.0+23067+0d16e377.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_aus:8.4::appstream","package":"redis-doc","fixed_in":["0:6.0.9-5.module+el8.4.0+23067+0d16e377.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_e4s:8.4::appstream","package":"redis","fixed_in":["0:6.0.9-5.module+el8.4.0+23067+0d16e377.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_e4s:8.4::appstream","package":"redis-debuginfo","fixed_in":["0:6.0.9-5.module+el8.4.0+23067+0d16e377.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_e4s:8.4::appstream","package":"redis-debugsource","fixed_in":["0:6.0.9-5.module+el8.4.0+23067+0d16e377.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_e4s:8.4::appstream","package":"redis-devel","fixed_in":["0:6.0.9-5.module+el8.4.0+23067+0d16e377.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_e4s:8.4::appstream","package":"redis-doc","fixed_in":["0:6.0.9-5.module+el8.4.0+23067+0d16e377.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_tus:8.4::appstream","package":"redis","fixed_in":["0:6.0.9-5.module+el8.4.0+23067+0d16e377.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_tus:8.4::appstream","package":"redis-debuginfo","fixed_in":["0:6.0.9-5.module+el8.4.0+23067+0d16e377.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_tus:8.4::appstream","package":"redis-debugsource","fixed_in":["0:6.0.9-5.module+el8.4.0+23067+0d16e377.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_tus:8.4::appstream","package":"redis-devel","fixed_in":["0:6.0.9-5.module+el8.4.0+23067+0d16e377.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_tus:8.4::appstream","package":"redis-doc","fixed_in":["0:6.0.9-5.module+el8.4.0+23067+0d16e377.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_aus:8.6::appstream","package":"redis","fixed_in":["0:6.0.9-5.module+el8.6.0+23072+c1b08039.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_aus:8.6::appstream","package":"redis-debuginfo","fixed_in":["0:6.0.9-5.module+el8.6.0+23072+c1b08039.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_aus:8.6::appstream","package":"redis-debugsource","fixed_in":["0:6.0.9-5.module+el8.6.0+23072+c1b08039.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_aus:8.6::appstream","package":"redis-devel","fixed_in":["0:6.0.9-5.module+el8.6.0+23072+c1b08039.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_aus:8.6::appstream","package":"redis-doc","fixed_in":["0:6.0.9-5.module+el8.6.0+23072+c1b08039.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_e4s:8.6::appstream","package":"redis","fixed_in":["0:6.0.9-5.module+el8.6.0+23072+c1b08039.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_e4s:8.6::appstream","package":"redis-debuginfo","fixed_in":["0:6.0.9-5.module+el8.6.0+23072+c1b08039.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_e4s:8.6::appstream","package":"redis-debugsource","fixed_in":["0:6.0.9-5.module+el8.6.0+23072+c1b08039.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_e4s:8.6::appstream","package":"redis-devel","fixed_in":["0:6.0.9-5.module+el8.6.0+23072+c1b08039.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_e4s:8.6::appstream","package":"redis-doc","fixed_in":["0:6.0.9-5.module+el8.6.0+23072+c1b08039.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_tus:8.6::appstream","package":"redis","fixed_in":["0:6.0.9-5.module+el8.6.0+23072+c1b08039.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_tus:8.6::appstream","package":"redis-debuginfo","fixed_in":["0:6.0.9-5.module+el8.6.0+23072+c1b08039.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_tus:8.6::appstream","package":"redis-debugsource","fixed_in":["0:6.0.9-5.module+el8.6.0+23072+c1b08039.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_tus:8.6::appstream","package":"redis-devel","fixed_in":["0:6.0.9-5.module+el8.6.0+23072+c1b08039.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_tus:8.6::appstream","package":"redis-doc","fixed_in":["0:6.0.9-5.module+el8.6.0+23072+c1b08039.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_e4s:9.0::appstream","package":"redis","fixed_in":["0:6.2.6-1.el9_0.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_e4s:9.0::appstream","package":"redis-debuginfo","fixed_in":["0:6.2.6-1.el9_0.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_e4s:9.0::appstream","package":"redis-debugsource","fixed_in":["0:6.2.6-1.el9_0.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_e4s:9.0::appstream","package":"redis-devel","fixed_in":["0:6.2.6-1.el9_0.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_e4s:9.0::appstream","package":"redis-doc","fixed_in":["0:6.2.6-1.el9_0.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_eus:8.8::appstream","package":"redis","fixed_in":["0:6.2.7-1.module+el8.8.0+23086+95b1dcd4.3"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_eus:8.8::appstream","package":"redis-debuginfo","fixed_in":["0:6.2.7-1.module+el8.8.0+23086+95b1dcd4.3"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_eus:8.8::appstream","package":"redis-debugsource","fixed_in":["0:6.2.7-1.module+el8.8.0+23086+95b1dcd4.3"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_eus:8.8::appstream","package":"redis-devel","fixed_in":["0:6.2.7-1.module+el8.8.0+23086+95b1dcd4.3"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_eus:8.8::appstream","package":"redis-doc","fixed_in":["0:6.2.7-1.module+el8.8.0+23086+95b1dcd4.3"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_eus:9.4::appstream","package":"redis","fixed_in":["0:6.2.7-1.el9_4.2","0:7.0.12-1.module+el9.4.0+23090+d27b104d.3"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_eus:9.4::appstream","package":"redis-debuginfo","fixed_in":["0:6.2.7-1.el9_4.2","0:7.0.12-1.module+el9.4.0+23090+d27b104d.3"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_eus:9.4::appstream","package":"redis-debugsource","fixed_in":["0:6.2.7-1.el9_4.2","0:7.0.12-1.module+el9.4.0+23090+d27b104d.3"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_eus:9.4::appstream","package":"redis-devel","fixed_in":["0:6.2.7-1.el9_4.2","0:7.0.12-1.module+el9.4.0+23090+d27b104d.3"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_eus:9.4::appstream","package":"redis-doc","fixed_in":["0:6.2.7-1.el9_4.2","0:7.0.12-1.module+el9.4.0+23090+d27b104d.3"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"redis","fixed_in":["0:6.2.7-1.el9_2.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"redis-debuginfo","fixed_in":["0:6.2.7-1.el9_2.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"redis-debugsource","fixed_in":["0:6.2.7-1.el9_2.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"redis-devel","fixed_in":["0:6.2.7-1.el9_2.2"],"sources":["osv"]},{"ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"redis-doc","fixed_in":["0:6.2.7-1.el9_2.2"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"redis","fixed_in":["0:7.2.8-1.module+el9.6.0+23049+8374f320","0:6.2.18-1.el9_6"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"redis-debuginfo","fixed_in":["0:7.2.8-1.module+el9.6.0+23049+8374f320","0:6.2.18-1.el9_6"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"redis-debugsource","fixed_in":["0:7.2.8-1.module+el9.6.0+23049+8374f320","0:6.2.18-1.el9_6"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"redis-devel","fixed_in":["0:7.2.8-1.module+el9.6.0+23049+8374f320","0:6.2.18-1.el9_6"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"redis-doc","fixed_in":["0:7.2.8-1.module+el9.6.0+23049+8374f320","0:6.2.18-1.el9_6"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:10.0","package":"valkey","fixed_in":["0:8.0.3-1.el10_0"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:10.0","package":"valkey-debuginfo","fixed_in":["0:8.0.3-1.el10_0"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:10.0","package":"valkey-debugsource","fixed_in":["0:8.0.3-1.el10_0"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:10.0","package":"valkey-devel","fixed_in":["0:8.0.3-1.el10_0"],"sources":["osv"]},{"ecosystem":"Red Hat:discovery:1.0::el8","package":"discovery-cli","fixed_in":["0:1.14.0-1.el8"],"sources":["osv"]},{"ecosystem":"Red Hat:discovery:1.0::el8","package":"discovery-installer","fixed_in":["0:1.14.1-1.el8"],"sources":["osv"]},{"ecosystem":"Red Hat:discovery:1.0::el9","package":"discovery-cli","fixed_in":["0:1.14.0-1.el9"],"sources":["osv"]},{"ecosystem":"Red Hat:discovery:1.0::el9","package":"discovery-installer","fixed_in":["0:1.14.1-1.el9"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:8::appstream","package":"redis","fixed_in":["0:6.2.18-1.module+el8.10.0+23050+05ea4e95"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:8::appstream","package":"redis-debuginfo","fixed_in":["0:6.2.18-1.module+el8.10.0+23050+05ea4e95"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:8::appstream","package":"redis-debugsource","fixed_in":["0:6.2.18-1.module+el8.10.0+23050+05ea4e95"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:8::appstream","package":"redis-devel","fixed_in":["0:6.2.18-1.module+el8.10.0+23050+05ea4e95"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:8::appstream","package":"redis-doc","fixed_in":["0:6.2.18-1.module+el8.10.0+23050+05ea4e95"],"sources":["osv"]},{"ecosystem":"Rocky Linux:9","package":"redis","fixed_in":["0:7.2.8-1.module+el9.6.0+32036+eb8f79e6","0:6.2.18-1.el9_6"],"sources":["osv"]},{"ecosystem":"Rocky Linux:10","package":"valkey","fixed_in":["0:8.0.3-1.el10_0"],"sources":["osv"]},{"ecosystem":"Rocky Linux:8","package":"redis","fixed_in":["0:6.2.18-1.module+el8.10.0+1980+8f0924a4"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"redis","fixed_in":["6.0.14-150200.6.35.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"redis","fixed_in":["6.0.14-150200.6.35.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"redis","fixed_in":["6.0.14-150200.6.35.1"],"sources":["osv"]},{"ecosystem":"SUSE:Enterprise Storage 7.1","package":"redis","fixed_in":["6.0.14-150200.6.35.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"redis7","fixed_in":["7.0.8-150500.3.18.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"redis7","fixed_in":["7.0.8-150500.3.18.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"redis7","fixed_in":["7.0.8-150500.3.18.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP5","package":"redis7","fixed_in":["7.0.8-150500.3.18.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"redis","fixed_in":["6.2.6-150400.3.34.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"redis","fixed_in":["6.2.6-150400.3.34.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"redis","fixed_in":["6.2.6-150400.3.34.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"redis","fixed_in":["6.2.6-150400.3.34.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"redis","fixed_in":["6.2.6-150400.3.34.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"redis","fixed_in":["6.2.6-150400.3.34.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"redis","fixed_in":["6.2.6-150400.3.34.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP5","package":"redis","fixed_in":["6.2.6-150400.3.34.1"],"sources":["osv"]},{"ecosystem":"SUSE:Manager Proxy 4.3","package":"redis","fixed_in":["6.2.6-150400.3.34.1"],"sources":["osv"]},{"ecosystem":"SUSE:Manager Server 4.3","package":"redis","fixed_in":["6.2.6-150400.3.34.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Module for Server Applications 15 SP6","package":"redis7","fixed_in":["7.0.8-150600.8.9.1"],"sources":["osv"]},{"ecosystem":"openSUSE:Leap 15.6","package":"redis7","fixed_in":["7.0.8-150600.8.9.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Module for Server Applications 15 SP6","package":"redis","fixed_in":["7.2.4-150600.3.9.1"],"sources":["osv"]},{"ecosystem":"openSUSE:Leap 15.6","package":"redis","fixed_in":["7.2.4-150600.3.9.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Module for Server Applications 15 SP6","package":"valkey","fixed_in":["8.0.2-150600.13.6.1"],"sources":["osv"]},{"ecosystem":"openSUSE:Leap 15.6","package":"valkey","fixed_in":["8.0.2-150600.13.6.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"valkey","fixed_in":["7.2.11+dfsg1-0ubuntu0.2"],"sources":["osv"]},{"ecosystem":"openSUSE:Tumbleweed","package":"valkey","fixed_in":["8.0.3-1.1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Alpine:v3.20","package":"redict","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.3.3-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.21","package":"redict","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.3.3-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.22","package":"redict","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.3.3-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.23","package":"redict","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.3.3-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.24","package":"redict","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.3.3-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.15","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.6.0"},{"fixed":"6.2.18-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.18","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.6.0"},{"fixed":"7.0.15-r3"}]}]},{"source":"osv","ecosystem":"Alpine:v3.19","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.6.0"},{"fixed":"7.2.8-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.20","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.6.0"},{"fixed":"7.2.8-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.21","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.6.0"},{"fixed":"7.2.8-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.22","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.6.0"},{"fixed":"8.0.0-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.23","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.6.0"},{"fixed":"8.0.0-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.24","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.6.0"},{"fixed":"8.0.0-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.20","package":"valkey","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"7.2.4"},{"fixed":"7.2.9-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.21","package":"valkey","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"7.2.4"},{"fixed":"7.2.9-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.22","package":"valkey","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"7.2.4"},{"fixed":"7.2.9-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.23","package":"valkey","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"7.2.4"},{"fixed":"7.2.9-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.24","package":"valkey","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"7.2.4"},{"fixed":"7.2.9-r0"}]}]},{"source":"osv","ecosystem":"AlmaLinux:9","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.2.8-1.module_el9.6.0+168+b8d8e900"}]}]},{"source":"osv","ecosystem":"AlmaLinux:9","package":"redis-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.2.8-1.module_el9.6.0+168+b8d8e900"}]}]},{"source":"osv","ecosystem":"AlmaLinux:9","package":"redis-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.2.8-1.module_el9.6.0+168+b8d8e900"}]}]},{"source":"osv","ecosystem":"AlmaLinux:9","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.2.18-1.el9_6"}]}]},{"source":"osv","ecosystem":"AlmaLinux:9","package":"redis-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.2.18-1.el9_6"}]}]},{"source":"osv","ecosystem":"AlmaLinux:9","package":"redis-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.2.18-1.el9_6"}]}]},{"source":"osv","ecosystem":"AlmaLinux:10","package":"valkey","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.0.3-1.el10_0"}]}]},{"source":"osv","ecosystem":"AlmaLinux:10","package":"valkey-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.0.3-1.el10_0"}]}]},{"source":"osv","ecosystem":"AlmaLinux:8","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.2.18-1.module_el8.10.0+3994+c2cc5395"}]}]},{"source":"osv","ecosystem":"AlmaLinux:8","package":"redis-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.2.18-1.module_el8.10.0+3994+c2cc5395"}]}]},{"source":"osv","ecosystem":"AlmaLinux:8","package":"redis-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.2.18-1.module_el8.10.0+3994+c2cc5395"}]}]},{"source":"osv","ecosystem":"Azure Linux:3","package":"valkey","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.0.3-1"}]}]},{"source":"osv","ecosystem":"Alpaquita:23","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"7.0.9-r0"},{"fixed":"7.0.15-r3"}]}]},{"source":"osv","ecosystem":"Alpaquita:stream","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"7.0.9-r0"},{"fixed":"8.0.0-r0"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"keydb","ranges":[{"type":"SEMVER","events":[{"introduced":"2.6.0"},{"fixed":"6.2.18"},{"introduced":"7.0.0"},{"fixed":"7.2.8"},{"introduced":"7.3.0"},{"fixed":"7.4.3"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"redis","ranges":[{"type":"SEMVER","events":[{"introduced":"2.6.0"},{"fixed":"6.2.18"},{"introduced":"7.0.0"},{"fixed":"7.2.8"},{"introduced":"7.3.0"},{"fixed":"6.2.18"},{"introduced":"7.2.0"},{"fixed":"7.2.8"},{"introduced":"7.4.0"},{"fixed":"7.4.3"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"valkey","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"7.2.9"},{"introduced":"8.0.0"},{"fixed":"8.0.3"},{"introduced":"8.1.0"},{"fixed":"8.1.1"}]}]},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.2.7-1.el9.tuxcare.els1"}]}]},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"redis-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.2.7-1.el9.tuxcare.els1"}]}]},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"redis-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.2.7-1.el9.tuxcare.els1"}]}]},{"source":"osv","ecosystem":"TuxCare:Debian:10","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5:5.0.14-1+deb10u5+tuxcare.els4"}]}],"bundled":4},{"source":"osv","ecosystem":"TuxCare:Debian:10","package":"redis-sentinel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5:5.0.14-1+deb10u5+tuxcare.els4"}]}],"bundled":4},{"source":"osv","ecosystem":"TuxCare:Debian:10","package":"redis-server","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5:5.0.14-1+deb10u5+tuxcare.els4"}]}],"bundled":4},{"source":"osv","ecosystem":"TuxCare:Debian:10","package":"redis-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5:5.0.14-1+deb10u5+tuxcare.els4"}]}],"bundled":4},{"source":"osv","ecosystem":"Debian:14","package":"redict","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.3.5+ds-1"}]}],"versions":["7.3.0+ds-1","7.3.0+ds-2","7.3.0+ds-3","7.3.0+ds-3~bpo12+1","7.3.1+ds-1","7.3.2+ds-1","7.3.2+ds-1~bpo12+1","7.3.5+ds-1~bpo12+1"]},{"source":"osv","ecosystem":"Debian:12","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5:7.0.15-1~deb12u4"}]}],"versions":["5:7.0.11-1","5:7.0.11-1+deb12u1","5:7.0.12-1","5:7.0.12-2","5:7.0.13-1","5:7.0.13-2","5:7.0.14-1","5:7.0.14-2","5:7.0.15-1~deb12u1","5:7.0.15-1~deb12u2","5:7.0.15-1~deb12u3"]},{"source":"osv","ecosystem":"Debian:13","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5:7.0.15-3.1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5:7.0.15-3.1"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"valkey","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.1.1+dfsg1-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"valkey","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.1.1+dfsg1-1"}]}]},{"source":"osv","ecosystem":"Debian:11","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5:6.0.16-1+deb11u6"}]}],"versions":["5:6.0.15-1","5:6.0.16-1","5:6.0.16-1+deb11u1","5:6.0.16-1+deb11u2","5:6.0.16-1+deb11u3","5:6.0.16-1+deb11u4","5:6.0.16-1+deb11u5","5:6.0.16-1~bpo10+1","5:6.0.16-1~bpo11+1"]},{"source":"osv","ecosystem":"Mageia:9","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.14-1.3.mga9"}]}]},{"source":"osv","ecosystem":"openEuler:20.03-LTS-SP4","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.2.8-1.oe2003sp4"}]}]},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP3","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.2.8-1.oe2203sp3"}]}]},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP4","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.2.8-1.oe2203sp4"}]}]},{"source":"osv","ecosystem":"openEuler:24.03-LTS","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.2.8-1.oe2403sp1"}]}]},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP1","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.2.8-1.oe2403sp1"}]}]},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP1","package":"redis6","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.2.7-6.oe2403sp1"}]}],"bundled":7},{"source":"osv","ecosystem":"openEuler:20.03-LTS-SP4","package":"redis6","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.2.7-4.oe2003sp4"}]}],"bundled":7},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP3","package":"redis6","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.2.7-6.oe2203sp3"}]}],"bundled":7},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP4","package":"redis6","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.2.7-6.oe2203sp4"}]}],"bundled":7},{"source":"osv","ecosystem":"openEuler:24.03-LTS","package":"redis6","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.2.7-6.oe2403"}]}],"bundled":7},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP2","package":"redis6","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.2.7-6.oe2403sp2"}]}],"bundled":6},{"source":"osv","ecosystem":"Red Hat:rhel_aus:8.4::appstream","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.0.9-5.module+el8.4.0+23067+0d16e377.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_aus:8.4::appstream","package":"redis-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.0.9-5.module+el8.4.0+23067+0d16e377.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_aus:8.4::appstream","package":"redis-debugsource","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.0.9-5.module+el8.4.0+23067+0d16e377.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_aus:8.4::appstream","package":"redis-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.0.9-5.module+el8.4.0+23067+0d16e377.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_aus:8.4::appstream","package":"redis-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.0.9-5.module+el8.4.0+23067+0d16e377.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_e4s:8.4::appstream","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.0.9-5.module+el8.4.0+23067+0d16e377.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_e4s:8.4::appstream","package":"redis-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.0.9-5.module+el8.4.0+23067+0d16e377.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_e4s:8.4::appstream","package":"redis-debugsource","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.0.9-5.module+el8.4.0+23067+0d16e377.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_e4s:8.4::appstream","package":"redis-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.0.9-5.module+el8.4.0+23067+0d16e377.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_e4s:8.4::appstream","package":"redis-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.0.9-5.module+el8.4.0+23067+0d16e377.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_tus:8.4::appstream","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.0.9-5.module+el8.4.0+23067+0d16e377.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_tus:8.4::appstream","package":"redis-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.0.9-5.module+el8.4.0+23067+0d16e377.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_tus:8.4::appstream","package":"redis-debugsource","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.0.9-5.module+el8.4.0+23067+0d16e377.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_tus:8.4::appstream","package":"redis-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.0.9-5.module+el8.4.0+23067+0d16e377.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_tus:8.4::appstream","package":"redis-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.0.9-5.module+el8.4.0+23067+0d16e377.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_aus:8.6::appstream","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.0.9-5.module+el8.6.0+23072+c1b08039.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_aus:8.6::appstream","package":"redis-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.0.9-5.module+el8.6.0+23072+c1b08039.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_aus:8.6::appstream","package":"redis-debugsource","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.0.9-5.module+el8.6.0+23072+c1b08039.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_aus:8.6::appstream","package":"redis-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.0.9-5.module+el8.6.0+23072+c1b08039.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_aus:8.6::appstream","package":"redis-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.0.9-5.module+el8.6.0+23072+c1b08039.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_e4s:8.6::appstream","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.0.9-5.module+el8.6.0+23072+c1b08039.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_e4s:8.6::appstream","package":"redis-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.0.9-5.module+el8.6.0+23072+c1b08039.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_e4s:8.6::appstream","package":"redis-debugsource","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.0.9-5.module+el8.6.0+23072+c1b08039.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_e4s:8.6::appstream","package":"redis-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.0.9-5.module+el8.6.0+23072+c1b08039.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_e4s:8.6::appstream","package":"redis-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.0.9-5.module+el8.6.0+23072+c1b08039.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_tus:8.6::appstream","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.0.9-5.module+el8.6.0+23072+c1b08039.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_tus:8.6::appstream","package":"redis-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.0.9-5.module+el8.6.0+23072+c1b08039.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_tus:8.6::appstream","package":"redis-debugsource","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.0.9-5.module+el8.6.0+23072+c1b08039.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_tus:8.6::appstream","package":"redis-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.0.9-5.module+el8.6.0+23072+c1b08039.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_tus:8.6::appstream","package":"redis-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.0.9-5.module+el8.6.0+23072+c1b08039.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_e4s:9.0::appstream","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.2.6-1.el9_0.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_e4s:9.0::appstream","package":"redis-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.2.6-1.el9_0.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_e4s:9.0::appstream","package":"redis-debugsource","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.2.6-1.el9_0.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_e4s:9.0::appstream","package":"redis-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.2.6-1.el9_0.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_e4s:9.0::appstream","package":"redis-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.2.6-1.el9_0.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::appstream","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.2.7-1.module+el8.8.0+23086+95b1dcd4.3"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::appstream","package":"redis-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.2.7-1.module+el8.8.0+23086+95b1dcd4.3"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::appstream","package":"redis-debugsource","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.2.7-1.module+el8.8.0+23086+95b1dcd4.3"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::appstream","package":"redis-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.2.7-1.module+el8.8.0+23086+95b1dcd4.3"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_eus:8.8::appstream","package":"redis-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.2.7-1.module+el8.8.0+23086+95b1dcd4.3"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.4::appstream","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.2.7-1.el9_4.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.4::appstream","package":"redis-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.2.7-1.el9_4.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.4::appstream","package":"redis-debugsource","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.2.7-1.el9_4.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.4::appstream","package":"redis-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.2.7-1.el9_4.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.4::appstream","package":"redis-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.2.7-1.el9_4.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.2.7-1.el9_2.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"redis-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.2.7-1.el9_2.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"redis-debugsource","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.2.7-1.el9_2.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"redis-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.2.7-1.el9_2.2"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.2::appstream","package":"redis-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.2.7-1.el9_2.2"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.2.8-1.module+el9.6.0+23049+8374f320"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"redis-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.2.8-1.module+el9.6.0+23049+8374f320"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"redis-debugsource","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.2.8-1.module+el9.6.0+23049+8374f320"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"redis-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.2.8-1.module+el9.6.0+23049+8374f320"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"redis-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.2.8-1.module+el9.6.0+23049+8374f320"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.2.18-1.el9_6"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"redis-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.2.18-1.el9_6"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"redis-debugsource","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.2.18-1.el9_6"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"redis-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.2.18-1.el9_6"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:9::appstream","package":"redis-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.2.18-1.el9_6"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"valkey","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:8.0.3-1.el10_0"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"valkey-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:8.0.3-1.el10_0"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"valkey-debugsource","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:8.0.3-1.el10_0"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:10.0","package":"valkey-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:8.0.3-1.el10_0"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.4::appstream","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.0.12-1.module+el9.4.0+23090+d27b104d.3"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.4::appstream","package":"redis-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.0.12-1.module+el9.4.0+23090+d27b104d.3"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.4::appstream","package":"redis-debugsource","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.0.12-1.module+el9.4.0+23090+d27b104d.3"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.4::appstream","package":"redis-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.0.12-1.module+el9.4.0+23090+d27b104d.3"}]}]},{"source":"osv","ecosystem":"Red Hat:rhel_eus:9.4::appstream","package":"redis-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.0.12-1.module+el9.4.0+23090+d27b104d.3"}]}]},{"source":"osv","ecosystem":"Red Hat:discovery:1.0::el8","package":"discovery-cli","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.14.0-1.el8"}]}]},{"source":"osv","ecosystem":"Red Hat:discovery:1.0::el8","package":"discovery-installer","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.14.1-1.el8"}]}]},{"source":"osv","ecosystem":"Red Hat:discovery:1.0::el9","package":"discovery-cli","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.14.0-1.el9"}]}]},{"source":"osv","ecosystem":"Red Hat:discovery:1.0::el9","package":"discovery-installer","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.14.1-1.el9"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::appstream","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.2.18-1.module+el8.10.0+23050+05ea4e95"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::appstream","package":"redis-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.2.18-1.module+el8.10.0+23050+05ea4e95"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::appstream","package":"redis-debugsource","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.2.18-1.module+el8.10.0+23050+05ea4e95"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::appstream","package":"redis-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.2.18-1.module+el8.10.0+23050+05ea4e95"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::appstream","package":"redis-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.2.18-1.module+el8.10.0+23050+05ea4e95"}]}]},{"source":"osv","ecosystem":"Rocky Linux:9","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.2.8-1.module+el9.6.0+32036+eb8f79e6"}]}]},{"source":"osv","ecosystem":"Rocky Linux:9","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.2.18-1.el9_6"}]}]},{"source":"osv","ecosystem":"Rocky Linux:10","package":"valkey","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:8.0.3-1.el10_0"}]}]},{"source":"osv","ecosystem":"Rocky Linux:8","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:6.2.18-1.module+el8.10.0+1980+8f0924a4"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Server Applications 15 SP7","package":"valkey","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.0.2-150700.3.5.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.0.14-150200.6.35.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.0.14-150200.6.35.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.0.14-150200.6.35.1"}]}]},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.0.14-150200.6.35.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"redis7","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.8-150500.3.18.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"redis7","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.8-150500.3.18.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"redis7","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.8-150500.3.18.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP5","package":"redis7","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.8-150500.3.18.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.2.6-150400.3.34.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.2.6-150400.3.34.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.2.6-150400.3.34.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.2.6-150400.3.34.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.2.6-150400.3.34.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.2.6-150400.3.34.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.2.6-150400.3.34.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP5","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.2.6-150400.3.34.1"}]}]},{"source":"osv","ecosystem":"SUSE:Manager Proxy 4.3","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.2.6-150400.3.34.1"}]}]},{"source":"osv","ecosystem":"SUSE:Manager Server 4.3","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.2.6-150400.3.34.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Server Applications 15 SP6","package":"redis7","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.8-150600.8.9.1"}]}]},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"redis7","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.8-150600.8.9.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Server Applications 15 SP6","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.2.4-150600.3.9.1"}]}]},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.2.4-150600.3.9.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Server Applications 15 SP6","package":"valkey","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.0.2-150600.13.6.1"}]}]},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"valkey","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.0.2-150600.13.6.1"}]}]},{"source":"osv","ecosystem":"Ubuntu:Pro:14.04:LTS","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2:2.6.13-1","2:2.6.16-3","2:2.8.0-1","2:2.8.2-1","2:2.8.4-2","2:2.8.4-2ubuntu0.2","2:2.8.4-2ubuntu0.2+esm1","2:2.8.4-2ubuntu0.2+esm2","2:2.8.4-2ubuntu0.2+esm3","2:2.8.4-2ubuntu0.2+esm4","2:2.8.4-2ubuntu0.2+esm5"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2:3.0.3-3","2:3.0.5-1","2:3.0.5-2","2:3.0.5-3","2:3.0.5-4","2:3.0.6-1","2:3.0.6-1ubuntu0.2","2:3.0.6-1ubuntu0.3","2:3.0.6-1ubuntu0.4","2:3.0.6-1ubuntu0.4+esm1","2:3.0.6-1ubuntu0.4+esm2","2:3.0.6-1ubuntu0.4+esm3","2:3.0.6-1ubuntu0.4+esm4","2:3.0.6-1ubuntu0.4+esm5"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4:4.0.1-7","4:4.0.2-6","4:4.0.2-9","5:4.0.5-1","5:4.0.6-1","5:4.0.6-2","5:4.0.7-1","5:4.0.8-1","5:4.0.8-2","5:4.0.9-1","5:4.0.9-1ubuntu0.1","5:4.0.9-1ubuntu0.2","5:4.0.9-1ubuntu0.2+esm2","5:4.0.9-1ubuntu0.2+esm3","5:4.0.9-1ubuntu0.2+esm4","5:4.0.9-1ubuntu0.2+esm5","5:4.0.9-1ubuntu0.2+esm6","5:4.0.9-1ubuntu0.2+esm7"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5:5.0.5-2build1","5:5.0.6-1","5:5.0.7-1","5:5.0.7-2","5:5.0.7-2ubuntu0.1~esm1","5:5.0.7-2ubuntu0.1","5:5.0.7-2ubuntu0.1+esm1","5:5.0.7-2ubuntu0.1+esm2","5:5.0.7-2ubuntu0.1+esm3","5:5.0.7-2ubuntu0.1+esm4"]},{"source":"osv","ecosystem":"Ubuntu:Pro:22.04:LTS","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5:6.0.15-1","5:6.0.16-1","5:6.0.16-1build1","5:6.0.16-1ubuntu1","5:6.0.16-1ubuntu1+esm1","5:6.0.16-1ubuntu1+esm2","5:6.0.16-1ubuntu1.1","5:6.0.16-1ubuntu1.1+esm1","5:6.0.16-1ubuntu1.2","5:6.0.16-1ubuntu1.2+esm1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5:7.0.12-1","5:7.0.14-1","5:7.0.14-2","5:7.0.15-1","5:7.0.15-1build1","5:7.0.15-1build2","5:7.0.15-1ubuntu0.24.04.1","5:7.0.15-1ubuntu0.24.04.2","5:7.0.15-1ubuntu0.24.04.3","5:7.0.15-1ubuntu0.24.04.4","5:7.0.15-1ubuntu0.24.04.5"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"valkey","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.2.11+dfsg1-0ubuntu0.2"}]}],"versions":["7.2.5+dfsg1-2ubuntu4~24.04.1","7.2.7+dfsg1-0ubuntu0.24.04.1","7.2.8+dfsg1-0ubuntu0.24.04.1","7.2.8+dfsg1-0ubuntu0.24.04.2","7.2.8+dfsg1-0ubuntu0.24.04.3","7.2.10+dfsg1-0ubuntu0.1","7.2.11+dfsg1-0ubuntu0.1"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"redict","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["7.3.2+ds-1","7.3.5+ds-1","7.3.5+ds-1ubuntu0.1","7.3.5+ds-1ubuntu0.2"]},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"redict","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["7.3.6+ds-1","7.3.6+ds-2","7.3.6+ds-2build1"]},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"valkey","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.0.3-1.1"}]}]},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"redis","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.0.2-1.1"}]}],"bundled":7}],"products":[{"vendor":"debian","product":"debian_linux"},{"vendor":"lfprojects","product":"valkey"},{"vendor":"redis","product":"redis"}],"references":[{"url":"https://github.com/redis/redis/security/advisories/GHSA-r67f-p999-2gff","tags":["x_refsource_CONFIRM","Third Party Advisory","advisory","article","report"]},{"url":"https://github.com/redis/redis/releases/tag/7.4.3","tags":["x_refsource_MISC","Release Notes","article","web","report"]},{"url":"https://lists.debian.org/debian-lts-announce/2025/05/msg00014.html","tags":["Mailing List","discussion","web"]},{"url":"https://github.com/valkey-io/valkey/releases/tag/8.1.1","tags":["Release Notes","article","web"]},{"url":"https://www.vicarius.io/vsociety/posts/cve-2025-21605-detection-script-memory-exhaustion-vulnerability-in-redis-database","tags":["web"]},{"url":"https://www.vicarius.io/vsociety/posts/cve-2025-21605-mitigation-script-memory-exhaustion-vulnerability-in-redis-database","tags":["web"]},{"url":"https://security.alpinelinux.org/vuln/CVE-2025-21605","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2025:7429","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2025-21605","tags":["report"]},{"url":"https://bugzilla.redhat.com/2361883","tags":["report"]},{"url":"https://errata.almalinux.org/9/ALSA-2025-7429.html","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2025:7438","tags":["advisory"]},{"url":"https://errata.almalinux.org/9/ALSA-2025-7438.html","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2025:7509","tags":["advisory"]},{"url":"https://errata.almalinux.org/10/ALSA-2025-7509.html","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2025:7686","tags":["advisory"]},{"url":"https://errata.almalinux.org/8/ALSA-2025-7686.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21605","tags":["web","advisory"]},{"url":"https://docs.bell-sw.com/security/cves/CVE-2025-21605","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/almalinux9.2esu/CLSA-2025-1750785864.html","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/debian10els/CLSA-2026-1788372462.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-48367","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-66373","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/21xxx/CVE-2025-21605.json","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2025-21605","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2025-0171.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=34243","tags":["report"]},{"url":"https://lists.suse.com/pipermail/sle-updates/2025-April/039118.html","tags":["web"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-1474","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-2837","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-32023","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-46817","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-46818","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-46819","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-49844","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-2838","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-2839","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-2840","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-2841","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-2862","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2025:4441","tags":["advisory"]},{"url":"https://access.redhat.com/security/updates/classification/#important","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2361883","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2025/rhsa-2025_4441.json","tags":["advisory"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-21605","tags":["advisory","report"]},{"url":"https://access.redhat.com/errata/RHSA-2025:4561","tags":["advisory"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2025/rhsa-2025_4561.json","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2025:4577","tags":["advisory"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2025/rhsa-2025_4577.json","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2025:4607","tags":["advisory"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2025/rhsa-2025_4607.json","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2025:4788","tags":["advisory"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2025/rhsa-2025_4788.json","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2025:4789","tags":["advisory"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2025/rhsa-2025_4789.json","tags":["advisory"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2025/rhsa-2025_7429.json","tags":["advisory"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2025/rhsa-2025_7438.json","tags":["advisory"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2025/rhsa-2025_7509.json","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2025:7538","tags":["advisory"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2025/rhsa-2025_7538.json","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2025:7630","tags":["advisory"]},{"url":"https://issues.redhat.com/browse/DISCOVERY-910","tags":["article"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2025/rhsa-2025_7630.json","tags":["advisory"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2025/rhsa-2025_7686.json","tags":["advisory"]},{"url":"https://errata.rockylinux.org/RLSA-2025:7429","tags":["advisory"]},{"url":"https://errata.rockylinux.org/RLSA-2025:7438","tags":["advisory"]},{"url":"https://errata.rockylinux.org/RLSA-2025:7509","tags":["advisory"]},{"url":"https://errata.rockylinux.org/RLSA-2025:7686","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202501942-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1241708","tags":["report"]},{"url":"https://bugzilla.suse.com/1243061","tags":["report"]},{"url":"https://bugzilla.suse.com/1243804","tags":["report"]},{"url":"https://bugzilla.suse.com/1243913","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21605","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-27151","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-49112","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202502010-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-20251419-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-20251420-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-20251432-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-20251433-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-20251566-1/","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2025-21605","tags":["report"]},{"url":"https://github.com/valkey-io/valkey/pull/1994","tags":["report"]},{"url":"https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/BSPBVBDGOIAOC7YYCCDLC4XBLWKHYLWL/","tags":["advisory"]},{"url":"","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2024-31227","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-31228","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-31449","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46981","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-51741","tags":["web"]}],"sources":{"cve":[{"id":"CVE-2025-21605","title":"Redis DoS Vulnerability due to unlimited growth of output buffers abused by unauthenticated client","description":"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.","status":"published","published":"2025-04-23T15:38:11.042Z","modified":"2026-02-10T17:06:50.695Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high","assessor":"cna"}],"cwes":["CWE-770"],"updated_at":"2026-11-02T14:32:32.702673Z"}],"euvd":[{"id":"EUVD-2025-12407","description":"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.","status":"published","published":"2025-04-23T15:38:11Z","modified":"2026-02-10T17:06:50Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T19:48:42.087959Z"}],"nvd":[{"id":"CVE-2025-21605","description":"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.","status":"published","published":"2025-04-23T16:15:34.77Z","modified":"2026-06-17T08:43:50.39Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high","assessor":"secondary"}],"cwes":["CWE-770"],"updated_at":"2026-11-02T14:11:01.507281Z"}],"osv":[{"id":"ALPINE-CVE-2025-21605","description":"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.","status":"published","published":"2025-04-23T16:15:34.77Z","modified":"2026-11-03T06:33:00.317303727Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-03T07:16:09.603409Z"},{"id":"BELL-CVE-2025-21605","status":"published","published":"2025-04-24T05:58:27.701423Z","modified":"2026-01-26T09:38:42.234377Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:28:21.227396Z"},{"id":"CVE-2025-21605","title":"Redis DoS Vulnerability due to unlimited growth of output buffers abused by unauthenticated client","description":"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.","status":"published","published":"2025-04-23T15:38:11.042Z","modified":"2026-10-28T02:30:49.521839956Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"cwes":["CWE-770"],"updated_at":"2026-11-02T15:44:46.665428Z"},{"id":"DEBIAN-CVE-2025-21605","description":"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.","status":"published","published":"2025-04-23T16:15:34.77Z","modified":"2026-09-01T20:05:41.922987855Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:45:45.102284Z"},{"id":"OESA-2025-1474","title":"redis security update","description":"Redis is an advanced key-value store. It is often referred to as a dattructure server since keys can contain strings, hashes ,lists, sets anorted sets.\r\n\r\nSecurity Fix(es):\n\nRedis 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 \u0026quot;NOAUTH\u0026quot; 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.(CVE-2025-21605)","status":"published","published":"2025-05-09T11:08:34Z","modified":"2026-08-18T01:18:50.545290099Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:42.714349Z"},{"id":"OESA-2025-2837","title":"redis6 security update","description":"Redis is an advanced key-value store. It is often referred to as a data structure server since keys can contain strings, hashes, lists, sets and sorted sets. You can run atomic operations on these types, like appending to a string; incrementing the value in a hash; pushing to a list; computing set intersection, union and difference; or getting the member with highest ranking in a sorted set. In order to achieve its outstanding performance, Redis works with an in-memory dataset. Depending on your use case, you can persist it either by dumping the dataset to disk every once in a while, or by appending each command to a log. Redis also supports trivial-to-setup master-slave replication, with very fast non-blocking first synchronization, auto-reconnection on net split and so forth. Other features include Transactions, Pub/Sub, Lua scripting, Keys with a limited time-to-live, and configuration settings to make Redis behave like a cache. You can use Redis from most programming languages also.\r\n\r\nSecurity Fix(es):\n\nRedis 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 \u0026quot;NOAUTH\u0026quot; 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.(CVE-2025-21605)\n\nRedis is an open source, in-memory database that persists on disk. From version 2.8 to before 8.0.3, 7.4.5, 7.2.10, and 6.2.19, an authenticated user may use a specially crafted string to trigger a stack/heap out of bounds write on hyperloglog operations, potentially leading to remote code execution. The bug likely affects all Redis versions with hyperloglog operations implemented. This vulnerability is fixed in 8.0.3, 7.4.5, 7.2.10, and 6.2.19.(CVE-2025-32023)\n\nRedis 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 cause an integer overflow and potentially lead to remote code execution. The problem exists in all versions of Redis with Lua scripting. This issue is fixed in version 8.2.2.(CVE-2025-46817)\n\nRedis 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.(CVE-2025-46818)\n\nRedis 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 read out-of-bound data or crash the server and subsequent denial of service. The problem exists in all versions of Redis with Lua scripting.(CVE-2025-46819)\n\nRedis is an open source, in-memory database that persists on disk. An unauthenticated connection can cause repeated IP protocol errors, leading to client starvation and, ultimately, a denial of service. This vulnerability is fixed in 8.0.3, 7.4.5, 7.2.10, and 6.2.19.(CVE-2025-48367)\n\nAn authenticated user may use a specially crafted Lua script to manipulate the garbage collector, trigger a use-after-free and potentially lead to remote code execution. The problem exists in all versions of Redis with Lua scripting.(CVE-2025-49844)","status":"published","published":"2025-12-12T11:09:58Z","modified":"2026-08-18T01:19:23.148940403Z","cvss":[{"version":"3.1","score":9.9,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:45.339366Z"},{"id":"OESA-2025-2838","title":"redis6 security update","description":"Redis is an advanced key-value store. It is often referred to as a data structure server since keys can contain strings, hashes, lists, sets and sorted sets. You can run atomic operations on these types, like appending to a string; incrementing the value in a hash; pushing to a list; computing set intersection, union and difference; or getting the member with highest ranking in a sorted set. In order to achieve its outstanding performance, Redis works with an in-memory dataset. Depending on your use case, you can persist it either by dumping the dataset to disk every once in a while, or by appending each command to a log. Redis also supports trivial-to-setup master-slave replication, with very fast non-blocking first synchronization, auto-reconnection on net split and so forth. Other features include Transactions, Pub/Sub, Lua scripting, Keys with a limited time-to-live, and configuration settings to make Redis behave like a cache. You can use Redis from most programming languages also.\r\n\r\nSecurity Fix(es):\n\nRedis 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 \u0026quot;NOAUTH\u0026quot; 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.(CVE-2025-21605)\n\nRedis is an open source, in-memory database that persists on disk. From version 2.8 to before 8.0.3, 7.4.5, 7.2.10, and 6.2.19, an authenticated user may use a specially crafted string to trigger a stack/heap out of bounds write on hyperloglog operations, potentially leading to remote code execution. The bug likely affects all Redis versions with hyperloglog operations implemented. This vulnerability is fixed in 8.0.3, 7.4.5, 7.2.10, and 6.2.19.(CVE-2025-32023)\n\nRedis 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 cause an integer overflow and potentially lead to remote code execution. The problem exists in all versions of Redis with Lua scripting. This issue is fixed in version 8.2.2.(CVE-2025-46817)\n\nRedis 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.(CVE-2025-46818)\n\nRedis 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 read out-of-bound data or crash the server and subsequent denial of service. The problem exists in all versions of Redis with Lua scripting.(CVE-2025-46819)\n\nRedis is an open source, in-memory database that persists on disk. An unauthenticated connection can cause repeated IP protocol errors, leading to client starvation and, ultimately, a denial of service. This vulnerability is fixed in 8.0.3, 7.4.5, 7.2.10, and 6.2.19.(CVE-2025-48367)\n\nAn authenticated user may use a specially crafted Lua script to manipulate the garbage collector, trigger a use-after-free and potentially lead to remote code execution. The problem exists in all versions of Redis with Lua scripting.(CVE-2025-49844)","status":"published","published":"2025-12-12T11:09:58Z","modified":"2026-08-18T01:19:23.168734781Z","cvss":[{"version":"3.1","score":9.9,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:45.339366Z"},{"id":"OESA-2025-2839","title":"redis6 security update","description":"Redis is an advanced key-value store. It is often referred to as a data structure server since keys can contain strings, hashes, lists, sets and sorted sets. You can run atomic operations on these types, like appending to a string; incrementing the value in a hash; pushing to a list; computing set intersection, union and difference; or getting the member with highest ranking in a sorted set. In order to achieve its outstanding performance, Redis works with an in-memory dataset. Depending on your use case, you can persist it either by dumping the dataset to disk every once in a while, or by appending each command to a log. Redis also supports trivial-to-setup master-slave replication, with very fast non-blocking first synchronization, auto-reconnection on net split and so forth. Other features include Transactions, Pub/Sub, Lua scripting, Keys with a limited time-to-live, and configuration settings to make Redis behave like a cache. You can use Redis from most programming languages also.\r\n\r\nSecurity Fix(es):\n\nRedis 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 \u0026quot;NOAUTH\u0026quot; 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.(CVE-2025-21605)\n\nRedis is an open source, in-memory database that persists on disk. From version 2.8 to before 8.0.3, 7.4.5, 7.2.10, and 6.2.19, an authenticated user may use a specially crafted string to trigger a stack/heap out of bounds write on hyperloglog operations, potentially leading to remote code execution. The bug likely affects all Redis versions with hyperloglog operations implemented. This vulnerability is fixed in 8.0.3, 7.4.5, 7.2.10, and 6.2.19.(CVE-2025-32023)\n\nRedis 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 cause an integer overflow and potentially lead to remote code execution. The problem exists in all versions of Redis with Lua scripting. This issue is fixed in version 8.2.2.(CVE-2025-46817)\n\nRedis 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.(CVE-2025-46818)\n\nRedis 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 read out-of-bound data or crash the server and subsequent denial of service. The problem exists in all versions of Redis with Lua scripting.(CVE-2025-46819)\n\nRedis is an open source, in-memory database that persists on disk. An unauthenticated connection can cause repeated IP protocol errors, leading to client starvation and, ultimately, a denial of service. This vulnerability is fixed in 8.0.3, 7.4.5, 7.2.10, and 6.2.19.(CVE-2025-48367)\n\nAn authenticated user may use a specially crafted Lua script to manipulate the garbage collector, trigger a use-after-free and potentially lead to remote code execution. The problem exists in all versions of Redis with Lua scripting.(CVE-2025-49844)","status":"published","published":"2025-12-12T11:09:58Z","modified":"2026-08-18T01:19:23.532149027Z","cvss":[{"version":"3.1","score":9.9,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:45.339366Z"},{"id":"OESA-2025-2840","title":"redis6 security update","description":"Redis is an advanced key-value store. It is often referred to as a data structure server since keys can contain strings, hashes, lists, sets and sorted sets. You can run atomic operations on these types, like appending to a string; incrementing the value in a hash; pushing to a list; computing set intersection, union and difference; or getting the member with highest ranking in a sorted set. In order to achieve its outstanding performance, Redis works with an in-memory dataset. Depending on your use case, you can persist it either by dumping the dataset to disk every once in a while, or by appending each command to a log. Redis also supports trivial-to-setup master-slave replication, with very fast non-blocking first synchronization, auto-reconnection on net split and so forth. Other features include Transactions, Pub/Sub, Lua scripting, Keys with a limited time-to-live, and configuration settings to make Redis behave like a cache. You can use Redis from most programming languages also.\r\n\r\nSecurity Fix(es):\n\nRedis 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 \u0026quot;NOAUTH\u0026quot; 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.(CVE-2025-21605)\n\nRedis is an open source, in-memory database that persists on disk. From version 2.8 to before 8.0.3, 7.4.5, 7.2.10, and 6.2.19, an authenticated user may use a specially crafted string to trigger a stack/heap out of bounds write on hyperloglog operations, potentially leading to remote code execution. The bug likely affects all Redis versions with hyperloglog operations implemented. This vulnerability is fixed in 8.0.3, 7.4.5, 7.2.10, and 6.2.19.(CVE-2025-32023)\n\nRedis 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 cause an integer overflow and potentially lead to remote code execution. The problem exists in all versions of Redis with Lua scripting. This issue is fixed in version 8.2.2.(CVE-2025-46817)\n\nRedis 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.(CVE-2025-46818)\n\nRedis 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 read out-of-bound data or crash the server and subsequent denial of service. The problem exists in all versions of Redis with Lua scripting.(CVE-2025-46819)\n\nRedis is an open source, in-memory database that persists on disk. An unauthenticated connection can cause repeated IP protocol errors, leading to client starvation and, ultimately, a denial of service. This vulnerability is fixed in 8.0.3, 7.4.5, 7.2.10, and 6.2.19.(CVE-2025-48367)\n\nAn authenticated user may use a specially crafted Lua script to manipulate the garbage collector, trigger a use-after-free and potentially lead to remote code execution. The problem exists in all versions of Redis with Lua scripting.(CVE-2025-49844)","status":"published","published":"2025-12-12T11:09:58Z","modified":"2026-08-18T01:19:23.179223022Z","cvss":[{"version":"3.1","score":9.9,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:45.339366Z"},{"id":"OESA-2025-2841","title":"redis6 security update","description":"Redis is an advanced key-value store. It is often referred to as a data structure server since keys can contain strings, hashes, lists, sets and sorted sets. You can run atomic operations on these types, like appending to a string; incrementing the value in a hash; pushing to a list; computing set intersection, union and difference; or getting the member with highest ranking in a sorted set. In order to achieve its outstanding performance, Redis works with an in-memory dataset. Depending on your use case, you can persist it either by dumping the dataset to disk every once in a while, or by appending each command to a log. Redis also supports trivial-to-setup master-slave replication, with very fast non-blocking first synchronization, auto-reconnection on net split and so forth. Other features include Transactions, Pub/Sub, Lua scripting, Keys with a limited time-to-live, and configuration settings to make Redis behave like a cache. You can use Redis from most programming languages also.\r\n\r\nSecurity Fix(es):\n\nRedis 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 \u0026quot;NOAUTH\u0026quot; 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.(CVE-2025-21605)\n\nRedis is an open source, in-memory database that persists on disk. From version 2.8 to before 8.0.3, 7.4.5, 7.2.10, and 6.2.19, an authenticated user may use a specially crafted string to trigger a stack/heap out of bounds write on hyperloglog operations, potentially leading to remote code execution. The bug likely affects all Redis versions with hyperloglog operations implemented. This vulnerability is fixed in 8.0.3, 7.4.5, 7.2.10, and 6.2.19.(CVE-2025-32023)\n\nRedis 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 cause an integer overflow and potentially lead to remote code execution. The problem exists in all versions of Redis with Lua scripting. This issue is fixed in version 8.2.2.(CVE-2025-46817)\n\nRedis 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.(CVE-2025-46818)\n\nRedis 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 read out-of-bound data or crash the server and subsequent denial of service. The problem exists in all versions of Redis with Lua scripting.(CVE-2025-46819)\n\nRedis is an open source, in-memory database that persists on disk. An unauthenticated connection can cause repeated IP protocol errors, leading to client starvation and, ultimately, a denial of service. This vulnerability is fixed in 8.0.3, 7.4.5, 7.2.10, and 6.2.19.(CVE-2025-48367)\n\nAn authenticated user may use a specially crafted Lua script to manipulate the garbage collector, trigger a use-after-free and potentially lead to remote code execution. The problem exists in all versions of Redis with Lua scripting.(CVE-2025-49844)","status":"published","published":"2025-12-12T11:09:58Z","modified":"2026-08-18T01:19:23.517101549Z","cvss":[{"version":"3.1","score":9.9,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:45.339366Z"},{"id":"OESA-2025-2862","title":"redis6 security update","description":"Redis is an advanced key-value store. It is often referred to as a data structure server since keys can contain strings, hashes, lists, sets and sorted sets. You can run atomic operations on these types, like appending to a string; incrementing the value in a hash; pushing to a list; computing set intersection, union and difference; or getting the member with highest ranking in a sorted set. In order to achieve its outstanding performance, Redis works with an in-memory dataset. Depending on your use case, you can persist it either by dumping the dataset to disk every once in a while, or by appending each command to a log. Redis also supports trivial-to-setup master-slave replication, with very fast non-blocking first synchronization, auto-reconnection on net split and so forth. Other features include Transactions, Pub/Sub, Lua scripting, Keys with a limited time-to-live, and configuration settings to make Redis behave like a cache. You can use Redis from most programming languages also.\r\n\r\nSecurity Fix(es):\n\nRedis 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 \u0026quot;NOAUTH\u0026quot; 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.(CVE-2025-21605)\n\nRedis is an open source, in-memory database that persists on disk. From version 2.8 to before 8.0.3, 7.4.5, 7.2.10, and 6.2.19, an authenticated user may use a specially crafted string to trigger a stack/heap out of bounds write on hyperloglog operations, potentially leading to remote code execution. The bug likely affects all Redis versions with hyperloglog operations implemented. This vulnerability is fixed in 8.0.3, 7.4.5, 7.2.10, and 6.2.19.(CVE-2025-32023)\n\nRedis 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 cause an integer overflow and potentially lead to remote code execution. The problem exists in all versions of Redis with Lua scripting. This issue is fixed in version 8.2.2.(CVE-2025-46817)\n\nRedis 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.(CVE-2025-46818)\n\nRedis 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 read out-of-bound data or crash the server and subsequent denial of service. The problem exists in all versions of Redis with Lua scripting.(CVE-2025-46819)\n\nRedis is an open source, in-memory database that persists on disk. An unauthenticated connection can cause repeated IP protocol errors, leading to client starvation and, ultimately, a denial of service. This vulnerability is fixed in 8.0.3, 7.4.5, 7.2.10, and 6.2.19.(CVE-2025-48367)","status":"published","published":"2025-12-30T11:09:59Z","modified":"2026-08-18T01:19:24.147679927Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:45.339366Z"},{"id":"RHSA-2025:4441","title":"Red Hat Security Advisory: redis:6 security update","status":"published","published":"2025-05-05T10:02:14Z","modified":"2026-10-16T10:08:53Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:17.133041Z"},{"id":"RHSA-2025:4561","title":"Red Hat Security Advisory: redis:6 security update","status":"published","published":"2025-05-07T10:05:48Z","modified":"2026-10-16T10:08:54Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:17.133041Z"},{"id":"RHSA-2025:4577","title":"Red Hat Security Advisory: redis security update","status":"published","published":"2025-05-07T10:05:51Z","modified":"2026-10-16T10:08:56Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:17.133041Z"},{"id":"RHSA-2025:4607","title":"Red Hat Security Advisory: redis:6 security update","status":"published","published":"2025-05-07T10:05:52Z","modified":"2026-10-16T10:08:57Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:17.133041Z"},{"id":"RHSA-2025:4788","title":"Red Hat Security Advisory: redis security update","status":"published","published":"2025-05-12T10:02:33Z","modified":"2026-10-16T10:08:59Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:17.133041Z"},{"id":"RHSA-2025:4789","title":"Red Hat Security Advisory: redis security update","status":"published","published":"2025-05-12T10:02:33Z","modified":"2026-10-16T10:08:59Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:17.133041Z"},{"id":"RHSA-2025:7429","title":"Red Hat Security Advisory: redis:7 security update","status":"published","published":"2025-05-14T10:06:22Z","modified":"2026-10-16T10:09:10Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:17.133041Z"},{"id":"RHSA-2025:7438","title":"Red Hat Security Advisory: redis security update","status":"published","published":"2025-05-14T10:06:27Z","modified":"2026-10-16T10:09:11Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:17.133041Z"},{"id":"RHSA-2025:7509","title":"Red Hat Security Advisory: valkey security update","status":"published","published":"2025-05-14T10:06:46Z","modified":"2026-10-16T10:09:17Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:17.133041Z"},{"id":"RHSA-2025:7538","title":"Red Hat Security Advisory: redis:7 security update","status":"published","published":"2025-05-14T10:06:55Z","modified":"2026-10-16T10:09:19Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:17.133041Z"},{"id":"RHSA-2025:7630","title":"Red Hat Security Advisory: updated discovery-cli RPMs","status":"published","published":"2025-05-15T10:04:00Z","modified":"2026-10-16T10:09:20Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:17.634515Z"},{"id":"RHSA-2025:7686","title":"Red Hat Security Advisory: redis:6 security update","status":"published","published":"2025-05-16T10:04:10Z","modified":"2026-10-16T10:09:21Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:17.634515Z"},{"id":"RLSA-2025:7429","title":"Important: redis:7 security update","description":"Redis is an advanced key-value store. It is often referred to as a data-structure server since keys can contain strings, hashes, lists, sets, and sorted sets. For performance, Redis works with an in-memory data set. You can persist it either by dumping the data set to disk every once in a while, or by appending each command to a log.\n\nSecurity Fix(es):\n\n* redis: Redis DoS Vulnerability due to unlimited growth of output buffers abused by unauthenticated client (CVE-2025-21605)\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.","status":"published","published":"2025-10-04T00:11:30.91642Z","modified":"2025-10-07T17:39:35.675804Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:25.216873Z"},{"id":"RLSA-2025:7438","title":"Important: redis security update","description":"Redis is an advanced key-value store. It is often referred to as a data-structure server since keys can contain strings, hashes, lists, sets, and sorted sets. For performance, Redis works with an in-memory data set. You can persist it either by dumping the data set to disk every once in a while, or by appending each command to a log.\n\nSecurity Fix(es):\n\n* redis: Redis DoS Vulnerability due to unlimited growth of output buffers abused by unauthenticated client (CVE-2025-21605)\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.","status":"published","published":"2025-10-04T00:11:30.91642Z","modified":"2025-10-07T17:39:36.760994Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:25.216873Z"},{"id":"RLSA-2025:7509","title":"Important: valkey security update","description":"Valkey is an advanced key-value store. It is often referred to as a data structure server since keys can contain strings, hashes, lists, sets and sorted sets.  You can run atomic operations on these types, like appending to a string; incrementing the value in a hash; pushing to a list; computing set intersection, union and difference; or getting the member with highest ranking in a sorted set.  In order to achieve its outstanding performance, Valkey works with an in-memory dataset. Depending on your use case, you can persist it either by dumping the dataset to disk every once in a while, or by appending each command to a log.  Valkey also supports trivial-to-setup master-slave replication, with very fast non-blocking first synchronization, auto-reconnection on net split and so forth.  Other features include Transactions, Pub/Sub, Lua scripting, Keys with a limited time-to-live, and configuration settings to make Valkey behave like a cache.  You can use Valkey from most programming languages also.\n\nSecurity Fix(es):\n\n* redis: Redis DoS Vulnerability due to unlimited growth of output buffers abused by unauthenticated client (CVE-2025-21605)\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.","status":"published","published":"2025-10-03T19:56:45.27031Z","modified":"2025-10-08T17:12:39.278851Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:25.508922Z"},{"id":"RLSA-2025:7686","title":"Important: redis:6 security update","description":"Redis is an advanced key-value store. It is often referred to as a data-structure server since keys can contain strings, hashes, lists, sets, and sorted sets. For performance, Redis works with an in-memory data set. You can persist it either by dumping the data set to disk every once in a while, or by appending each command to a log.\n\nSecurity Fix(es):\n\n* redis: Redis DoS Vulnerability due to unlimited growth of output buffers abused by unauthenticated client (CVE-2025-21605)\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.","status":"published","published":"2025-07-29T13:38:41.630147Z","modified":"2025-07-29T15:00:09.419124Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:25.508922Z"},{"id":"UBUNTU-CVE-2025-21605","description":"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.","status":"published","published":"2025-04-23T16:15:00Z","modified":"2026-11-09T12:49:26.473928873Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-09T13:27:42.046613Z"},{"id":"ALSA-2025:7429","title":"Important: redis:7 security update","description":"Redis is an advanced key-value store. It is often referred to as a data-structure server since keys can contain strings, hashes, lists, sets, and sorted sets. For performance, Redis works with an in-memory data set. You can persist it either by dumping the data set to disk every once in a while, or by appending each command to a log.  \n\nSecurity Fix(es):  \n\n  * redis: Redis DoS Vulnerability due to unlimited growth of output buffers abused by unauthenticated client (CVE-2025-21605)\n\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.\n","status":"published","published":"2025-05-13T00:00:00Z","modified":"2026-10-29T11:32:16.411661252Z","updated_at":"2026-11-02T15:27:53.448565Z"},{"id":"ALSA-2025:7438","title":"Important: redis security update","description":"Redis is an advanced key-value store. It is often referred to as a data-structure server since keys can contain strings, hashes, lists, sets, and sorted sets. For performance, Redis works with an in-memory data set. You can persist it either by dumping the data set to disk every once in a while, or by appending each command to a log.  \n\nSecurity Fix(es):  \n\n  * redis: Redis DoS Vulnerability due to unlimited growth of output buffers abused by unauthenticated client (CVE-2025-21605)\n\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.\n","status":"published","published":"2025-05-13T00:00:00Z","modified":"2026-10-29T11:32:16.479494684Z","updated_at":"2026-11-02T15:27:53.448565Z"},{"id":"ALSA-2025:7509","title":"Important: valkey security update","description":"Valkey is an advanced key-value store. It is often referred to as a data structure server since keys can contain strings, hashes, lists, sets and sorted sets. You can run atomic operations on these types, like appending to a string; incrementing the value in a hash; pushing to a list; computing set intersection, union and difference; or getting the member with highest ranking in a sorted set. In order to achieve its outstanding performance, Valkey works with an in-memory dataset. Depending on your use case, you can persist it either by dumping the dataset to disk every once in a while, or by appending each command to a log. Valkey also supports trivial-to-setup master-slave replication, with very fast non-blocking first synchronization, auto-reconnection on net split and so forth. Other features include Transactions, Pub/Sub, Lua scripting, Keys with a limited time-to-live, and configuration settings to make Valkey behave like a cache. You can use Valkey from most programming languages also.  \n\nSecurity Fix(es):  \n\n  * redis: Redis DoS Vulnerability due to unlimited growth of output buffers abused by unauthenticated client (CVE-2025-21605)\n\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.\n","status":"published","published":"2025-05-13T00:00:00Z","modified":"2026-10-29T11:58:18.009657Z","updated_at":"2026-11-02T15:27:53.448565Z"},{"id":"ALSA-2025:7686","title":"Important: redis:6 security update","description":"Redis is an advanced key-value store. It is often referred to as a data-structure server since keys can contain strings, hashes, lists, sets, and sorted sets. For performance, Redis works with an in-memory data set. You can persist it either by dumping the data set to disk every once in a while, or by appending each command to a log.  \n\nSecurity Fix(es):  \n\n  * redis: Redis DoS Vulnerability due to unlimited growth of output buffers abused by unauthenticated client (CVE-2025-21605)\n\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.\n","status":"published","published":"2025-05-15T00:00:00Z","modified":"2026-10-29T11:02:23.202553858Z","updated_at":"2026-11-02T15:27:53.448565Z"},{"id":"AZL-60939","title":"CVE-2025-21605 affecting package valkey for versions less than 8.0.3-1","description":"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.","status":"published","published":"2025-04-23T16:15:34Z","modified":"2026-04-21T04:48:36.863287Z","updated_at":"2026-11-02T15:28:07.517393Z"},{"id":"BIT-keydb-2025-21605","title":"Redis DoS Vulnerability due to unlimited growth of output buffers abused by unauthenticated client","description":"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.","status":"published","published":"2025-04-25T07:14:30.296Z","modified":"2026-09-08T08:48:07.654446965Z","updated_at":"2026-11-02T15:28:32.162822Z"},{"id":"BIT-redis-2025-21605","title":"Redis DoS Vulnerability due to unlimited growth of output buffers abused by unauthenticated client","description":"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.","status":"published","published":"2025-04-25T07:24:43.793Z","modified":"2026-09-08T08:48:19.144403656Z","updated_at":"2026-11-02T15:28:35.111822Z"},{"id":"BIT-valkey-2025-21605","title":"Redis DoS Vulnerability due to unlimited growth of output buffers abused by unauthenticated client","description":"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.","status":"published","published":"2025-04-25T07:27:01.789Z","modified":"2026-09-08T08:48:21.005245822Z","updated_at":"2026-11-02T15:28:36.104787Z"},{"id":"CLSA-2025-1750785864","title":"redis: Fix of CVE-2025-21605","description":"- CVE-2025-21605: add output buffer limiting for unauthenticated clients","status":"published","published":"2025-06-24T17:24:29Z","modified":"2026-06-01T00:30:53.399920449Z","updated_at":"2026-11-02T15:43:41.66212Z"},{"id":"CLSA-2026-1788372462","title":"Fix CVE(s): CVE-2025-21605, CVE-2025-48367, CVE-2026-66373","description":"   * SECURITY UPDATE: Memory exhaustion via unauthenticated client output buffer\n     - debian/patches/0016-CVE-2025-21605.patch: cap the output buffer of\n       unauthenticated clients in checkClientOutputBufferLimits() in\n       src/networking.c, so a client that never reads its NOAUTH replies\n       cannot grow the buffer without bound. Backport of upstream redis\n       commit 5e93f9cb9 (6.2.18) as shipped by Debian for bullseye in\n       5:6.0.16-1+deb11u9 (DLA-4162-1), adapted to 5.0 by spelling the\n       condition as server.requirepass \u0026\u0026 !c-\u003eauthenticated, since 5.0\n       predates the ACL subsystem and has no authRequired() helper.\n     - CVE-2025-21605\n   * SECURITY UPDATE: Client starvation via repeated accept() errors\n     - debian/patches/0017-CVE-2025-48367.patch: add\n       anetAcceptFailureNeedsRetry() to src/anet.c and retry the accept\n       loop in acceptTcpHandler()/acceptUnixHandler() in src/networking.c\n       and clusterAcceptHandler() in src/cluster.c, so a connection that\n       fails at accept() time no longer aborts the whole batch and starves\n       other pending clients. Backport of upstream redis commit 0fe674359\n       (6.2.19) as shipped by Debian for bullseye in 5:6.0.16-1+deb11u9\n       (DLA-4240-1); the acceptTLSHandler() hunk is dropped because 5.0\n       has no TLS support.\n     - CVE-2025-48367\n   * SECURITY UPDATE: Double free via stream RDB payload with a shared NACK\n     - debian/patches/0018-CVE-2026-66373.patch: reject a stream payload\n       whose consumer PELs reference the same global-PEL NACK twice, in\n       rdbLoadObject() in src/rdb.c, so RESTORE can no longer build two\n       consumers sharing one streamNACK and have XGROUP DELCONSUMER free\n       it twice. Backport of upstream redis commit 41a958720 (6.2.23) as\n       shipped by Debian for bullseye and bookworm in 5:6.0.16-1+deb11u9\n       and 5:7.0.15-1~deb12u9 (DLA-4722-1), taken verbatim in the Debian\n       form that uses rdbExitReportCorruptRDB(). Note this CVE exists\n       because of an incomplete fix for CVE-2026-25243, which is a\n       separate change and is not addressed here.\n     - CVE-2026-66373","status":"published","published":"2026-09-02T18:07:54Z","modified":"2026-10-26T09:43:18.682215829Z","updated_at":"2026-11-02T15:43:47.591214Z"},{"id":"DLA-4162-1","title":"redis - security update","status":"published","published":"2025-05-12T00:00:00Z","modified":"2026-03-09T01:22:12.843428Z","updated_at":"2026-11-02T15:46:12.7027Z"},{"id":"MGASA-2025-0171","title":"Updated redis packages fix security vulnerability","description":"Redis DoS Vulnerability due to unlimited growth of output buffers abused\nby unauthenticated client. (CVE-2025-21605)\n","status":"published","published":"2025-05-31T03:36:06Z","modified":"2026-05-16T06:30:38.738251Z","updated_at":"2026-11-02T15:49:43.178336Z"},{"id":"openSUSE-SU-2025:15035-1","title":"valkey-8.0.3-1.1 on GA media","description":"These are all security issues fixed in the valkey-8.0.3-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2025-04-26T00:00:00Z","modified":"2026-02-04T02:27:30.301217Z","updated_at":"2026-11-02T16:58:37.399567Z"},{"id":"openSUSE-SU-2025:15293-1","title":"redis-8.0.2-1.1 on GA media","description":"These are all security issues fixed in the redis-8.0.2-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2025-07-03T00:00:00Z","modified":"2026-03-23T04:53:36.205134Z","updated_at":"2026-11-02T16:58:37.810934Z"},{"id":"SUSE-SU-2025:01942-1","title":"Security update for valkey","description":"This update for valkey fixes the following issues:\n\n- CVE-2025-27151: Absence of filename size check may cause a stack\n  overflow (bsc#1243804)\n- CVE-2025-49112: setDeferredReply integer underflow (bsc#1243913)\n- CVE-2025-21605: Output buffer denial of service (bsc#1241708)\n","status":"published","published":"2025-06-13T08:33:49Z","modified":"2026-03-23T04:48:30.050805Z","updated_at":"2026-11-02T15:53:56.647031Z"},{"id":"SUSE-SU-2025:02010-1","title":"Security update for redis","description":"This update for redis fixes the following issues:\n\n- CVE-2025-21605: output buffer denial of service (bsc#1241708).\n","status":"published","published":"2025-06-18T15:25:25Z","modified":"2026-02-04T03:44:10.570641Z","updated_at":"2026-11-02T15:53:56.647031Z"},{"id":"SUSE-SU-2025:1419-1","title":"Security update for redis","description":"This update for redis fixes the following issues:\n\n- CVE-2025-21605: Fixed an output buffer denial of service. (bsc#1241708)\n","status":"published","published":"2025-04-30T12:55:00Z","modified":"2026-02-04T03:08:12.487484Z","updated_at":"2026-11-02T15:53:59.381172Z"},{"id":"SUSE-SU-2025:1420-1","title":"Security update for redis","description":"This update for redis fixes the following issues:\n\n- CVE-2025-21605: Fixed an output buffer denial of service. (bsc#1241708)\n","status":"published","published":"2025-04-30T12:55:40Z","modified":"2026-02-04T04:14:25.95227Z","updated_at":"2026-11-02T15:53:59.381172Z"},{"id":"SUSE-SU-2025:1432-1","title":"Security update for redis","description":"This update for redis fixes the following issues:\n\n- CVE-2025-21605: Fixed an output buffer denial of service. (bsc#1241708)\n","status":"published","published":"2025-05-02T10:23:30Z","modified":"2026-03-23T04:47:04.924544Z","updated_at":"2026-11-02T15:53:59.381172Z"},{"id":"SUSE-SU-2025:1433-1","title":"Security update for redis","description":"This update for redis fixes the following issues:\n\n- CVE-2025-21605: Fixed an output buffer denial of service. (bsc#1241708)\n","status":"published","published":"2025-05-02T10:23:46Z","modified":"2026-03-23T04:50:00.594113Z","updated_at":"2026-11-02T15:53:59.381172Z"},{"id":"SUSE-SU-2025:1566-1","title":"Security update for valkey","description":"This update for valkey fixes the following issues:\n\n- CVE-2025-21605: Fixed output buffer denial of service (bsc#1241708)\n","status":"published","published":"2025-05-16T12:02:15Z","modified":"2026-02-04T02:57:02.178775Z","updated_at":"2026-11-02T15:53:59.381172Z"}]}}