Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
🔗 CVE IDs covered (6)
📋 Description
CVE-2026-56684 — valkey: Valkey: Remote code execution via TLS pending-data processing use-after-free CVE-2026-63639 — valkey: Valkey: Remote code execution via use-after-free in stream deserialization CVE-2026-82631 — valkey: Valkey: Use-after-free vulnerability in Blocked-on-keys subsystem CVE-2026-82677 — valkey: Valkey: Denial of Service via double free in Module Timer subsystem CVE-2026-85522 — valkey: Valkey: Remote out-of-bounds read in Slot Migration can lead to denial of service CVE-2026-86227 — valkey: Valkey: Denial of Service due to out-of-bounds read
🎯 Affected products14
- Red Hat Hardened Images
- valkey-0:9.0.6-0.1.hum1@aarch64 as a component of Red Hat Hardened Images
- valkey-0:9.0.6-0.1.hum1@src as a component of Red Hat Hardened Images
- valkey-0:9.0.6-0.1.hum1@x86_64 as a component of Red Hat Hardened Images
- valkey-compat-redis-0:9.0.6-0.1.hum1@noarch@public-hummingbird-aarch64-rpms as a component of Red Hat Hardened Images
- valkey-compat-redis-0:9.0.6-0.1.hum1@noarch@public-hummingbird-x86_64-rpms as a component of Red Hat Hardened Images
- valkey-compat-redis-devel-0:9.0.6-0.1.hum1@noarch@public-hummingbird-aarch64-rpms as a component of Red Hat Hardened Images
- valkey-compat-redis-devel-0:9.0.6-0.1.hum1@noarch@public-hummingbird-x86_64-rpms as a component of Red Hat Hardened Images
- valkey-devel-0:9.0.6-0.1.hum1@aarch64 as a component of Red Hat Hardened Images
- valkey-devel-0:9.0.6-0.1.hum1@x86_64 as a component of Red Hat Hardened Images
- valkey-doc-0:9.0.6-0.1.hum1@noarch@public-hummingbird-aarch64-rpms as a component of Red Hat Hardened Images
- valkey-doc-0:9.0.6-0.1.hum1@noarch@public-hummingbird-x86_64-rpms as a component of Red Hat Hardened Images
- valkey-rdma-0:9.0.6-0.1.hum1@aarch64 as a component of Red Hat Hardened Images
- valkey-rdma-0:9.0.6-0.1.hum1@x86_64 as a component of Red Hat Hardened Images
✅ Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Workaround: Restrict network access to the Valkey instance to trusted clients and networks by configuring firewall rules to limit inbound connections to the Valkey service port. Ensure only authorized and authenticated clients can connect. If TLS is not strictly required, consider disabling it. These network restrictions will persist if the Valkey service is reloaded or restarted. Workaround: To mitigate this issue, restrict network access to the Valkey instance to only trusted clients and networks. This limits an attacker's ability to send malformed RDB stream payloads to the RESTORE command. Implement firewall rules to block unauthorized access to the Valkey port. Workaround: Restrict access to high-privilege administrative users capable of executing module timer operations, or isolate the Valkey service using network firewalls and RBAC controls until fixed packages are installed. Workaround: Restrict access to the Valkey cluster communication port using network firewalls so only trusted cluster nodes can interact with the migration interface. Additionally, configure Valkey ACLs to restrict untrusted clients from invoking cluster migration commands.
🔗 References (10)
- selfhttps://access.redhat.com/errata/RHSA-2026:61884
- externalhttps://access.redhat.com/security/cve/CVE-2026-85522
- externalhttps://access.redhat.com/security/updates/classification/
- externalhttps://access.redhat.com/security/cve/CVE-2026-86227
- externalhttps://access.redhat.com/security/cve/CVE-2026-56684
- externalhttps://access.redhat.com/security/cve/CVE-2026-63639
- externalhttps://access.redhat.com/security/cve/CVE-2026-82677
- externalhttps://images.redhat.com/
- externalhttps://access.redhat.com/security/cve/CVE-2026-82631
- selfhttps://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_61884.json