CVE-2026-23479VulnerabilityPublished 16 Jun 2026Updated 29 Oct 2026

Red Hat Security Advisory: redis:7 security update

Affects Red Hat redis:7Source GCVE Database

Compare

Mentioned vulnerabilities

Not known to be exploited.

Data as of 29 Oct 2026, 16:10 UTC

Severity

High

Rated by Threat Radar · No CVSS score from NVD or the CNA

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Red Hat has released updated Redis 7 packages as part of Red Hat Enterprise Linux 9.6 Extended Update Support to fix these vulnerabilities. Users should apply these official updates promptly. For detailed update instructions, refer to Red Hat's advisory and article at https://access.redhat.com/articles/11258. No additional mitigations are specified beyond applying the official patches.

Description

Multiple use-after-free and invalid memory access vulnerabilities in Redis 7 have been addressed by Red Hat in their Enterprise Linux 9.6 Extended Update Support release. These flaws may allow remote code execution. The update fixes three specific CVEs: CVE-2026-23479, CVE-2026-23631, and CVE-2026-25243. Red Hat rates the security impact as Important and provides updated packages to remediate these issues.

Impact

Successful exploitation of these vulnerabilities could allow remote attackers to execute arbitrary code on affected systems running Redis 7. This poses a significant risk to system confidentiality, integrity, and availability. Red Hat classifies the impact as Important, indicating a high severity level requiring prompt attention.

Summary

Redis, an advanced key-value store, had several critical security issues involving use-after-free vulnerabilities and invalid memory access that could lead to remote code execution. Specifically, CVE-2026-23479 involves a use-after-free in the unblock client flow, CVE-2026-23631 involves use-after-free in Lua scripting, and CVE-2026-25243 involves invalid memory access in the RESTORE command. Red Hat has released security updates for Redis 7 as part of Red Hat Enterprise Linux 9.6 Extended Update Support to address these vulnerabilities.

CWE-416Use After Free (opens in a new tab)
Variant weaknessLikelihood of exploit: HighCWE Top 25 (2025): #7
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Architecture and Design · Language Selection
Choose a language that provides automatic memory management.
Implementation · Attack Surface Reduction
When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-122Heap-based Buffer Overflow (opens in a new tab)
Variant weaknessLikelihood of exploit: HighCWE Top 25 (2025): #16
The product writes past the end of a buffer that was allocated on the heap.
Pre-design: Use a language or compiler that performs automatic bounds checking.
Architecture and Design
Use an abstraction library to abstract away risky APIs. Not a complete solution.
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Forced Integer Overflow (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 29 Oct 2026, 16:10 UTC

Public exploits and detectionGitHub proofs of concept

WeaknessesCWE-416, CWE-122

Technical details

References

Community reviews

Related threats