Hey,
https://github.com/redis/redis/releases/tag/6.2.22
Update urgency: SECURITY: There is a security fix in the release.
Security fixes
(CVE-2026-25243) Invalid memory access in RESTORE may lead to
Remote Code Execution
Bug fixes
SUBSCRIBE, PSUBSCRIBE, SSUBSCRIBE: crash on OOM (RED-167788)
SCRIPT DEBUG: potential crash on scripts (RED-175507)
Index: Makefile
===================================================================
RCS file: /cvs/ports/databases/redis/Makefile,v
diff -u -p -r1.142 Makefile
--- Makefile 3 Nov 2025 00:50:55 -0000 1.142
+++ Makefile 5 May 2026 14:31:51 -0000
@@ -1,6 +1,6 @@
COMMENT = persistent key-value database
-DISTNAME = redis-6.2.21
+DISTNAME = redis-6.2.22
CATEGORIES = databases
HOMEPAGE = https://redis.io/
Index: distinfo
===================================================================
RCS file: /cvs/ports/databases/redis/distinfo,v
diff -u -p -r1.112 distinfo
--- distinfo 3 Nov 2025 00:50:55 -0000 1.112
+++ distinfo 5 May 2026 14:31:51 -0000
@@ -1,2 +1,2 @@
-SHA256 (redis-6.2.21.tar.gz) = Y4OzK6jSRvQbu7g2YzgfWl9MRxMjVDPOwi/EpH6bbV8=
-SIZE (redis-6.2.21.tar.gz) = 2496176
+SHA256 (redis-6.2.22.tar.gz) = POGRpydQWy1xG7Rc/ejZ7qseBhvcDly1alAgEGmpcp0=
+SIZE (redis-6.2.22.tar.gz) = 2498476
I'll commit it to -current once the tree is open again. I'm sending the
diff:
* in case someone wants to update their infra running -current
* hopefully someone volunteers to commit with the relevant -stable cvs
tag :) (I assume that person will have to 'volunteer' to commit to
the new release's -stable branch once it opens as well?)
Cheers,
Daniel
