Redis: Security Patches and Replication Hardening
A critical stream restore vulnerability was patched across three release branches, while a cluster of fixes tightened up replication accuracy, connection handling, and durability during startup.
Duration: PT2M37S
Episode overview
This episode is a short developer briefing from Redis.
It explains recent repository work in plain language.
- Show: Redis
- Published: 2026-07-24T13:12:28Z
- Audio duration: PT2M37S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
This is Redis News for July 24th, 2026.
The top story tonight is security. Redis shipped patches for versions 7.2, 7.4, and 6.2 after finding that a crafted stream restore payload could let two consumers share the same NACK — a use-after-free bug that could lead to remote code execution. If you're running self-managed Redis on any of those branches, this…
Beyond the security fix, the biggest theme this cycle is replication accuracy — making sure Redis's internal accounting and topology actually match reality. PR 15499 fixes client memory reporting: compressed replication links were under-reporting their true memory footprint by roughly a factor of one hundred,…
The second theme is startup and connection durability. Commit 53f7e0a, from PR 15509, changes how preload-file data gets installed — instead of forcing a full AOF rewrite at startup, Redis now rebuilds the local AOF manifest directly from the preload source, using hard links where possible. That trims startup cost…
Rounding things out, the RedisBloom module pin was bumped across five branch lines — 8.2 through 8.10 — mainly to pull in hardened RDB loading and a fix so Cuckoo Filter chunks replicate correctly during failover.
Wha…
Nearby episodes from Redis
- TLS Cluster Ports Get Module Visibility
- Waking Sleepers and Closing Edge Cases
- Protocol Correctness and Replication Memory Accounting
- Replication Compression Lands, Durability Bugs Squashed
- Weekly Recap - Replication, Persistence, and Memory Efficiency
- Build Environment Cleanup
- Storage Overhauls and a Security Patch
- Correctness Fixes and a Module Refresh