CVE-2025-32023VulnerabilityPublished 21 Jul 2025Updated 11 Oct 2026

SUSE · security update for redis

Affects SUSESource GCVE Database

Mentioned vulnerabilities

CVE-2025-48367

Public exploit available (Exploit-DB) · fixed in SUSE package updates : patch SUSE as a priority.

Data as of 26 Oct 2026, 10:12 UTC

Severity

High

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

EPSS: 6.4% chance of exploitation in 30 days – higher than 93% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 8.0.3, 7.4.5, 7.2.10 +2

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

Disclosed: evidence found.
CVE published 21 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
1 Exploit-DB entry, 198 days after disclosure
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

CVE published
on cve.org
21 Jul 2025, t = 0
First Exploit-DB entry (opens in a new tab)
Redis 8.0.2 - RCE
4 Feb 2026, 198 days after disclosure

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 26 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
SUSE Product Security Team SUSE	Affected >=6.2.19 <6.2.20 Red Hat Red Hat Quay Quay v3 s390x quay/quay-bridge-operator-bundle@sha256:fdc74412fb2da7c215728fac91583905ef25186972fab633c102e06a1245ccf0_s390x >=2.8.0 <6.2.19 >=7.0.0 <7.2.10 >=8.0.0 <8.0.3 >=7.4.0 <7.4.5 SUSE i686 redis-devel-0:6.2.19-1.el9_6.i686 noarch redis-doc-0:6.2.19-1.el9_6.noarch	Fixed in 6.2.20 6.2.19 7.2.10 8.0.3 7.4.5

AI-suggested

Red Hat has released updated Redis packages for Red Hat Enterprise Linux 8 that address these vulnerabilities. Users should apply the provided updates as per Red Hat's instructions at https://access.redhat.com/articles/11258. No additional mitigation steps are indicated or required beyond applying the official update.

Description

Redis is an open source, in-memory database that persists on disk. From 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. An additional workaround to mitigate the problem without patching the redis-server executable is to prevent users from executing hyperloglog operations. This can be done using ACL to restrict HLL commands.

Impact

The vulnerabilities could allow an unauthenticated attacker to cause denial of service or potentially corrupt memory via an out-of-bounds write, impacting Redis service availability and integrity. No known exploits in the wild have been reported. The impact is rated as important by Red Hat, indicating a significant security concern but not necessarily critical.

Summary

This advisory covers two security vulnerabilities in Redis 6 as packaged for Red Hat Enterprise Linux 8. CVE-2025-48367 is an unauthenticated denial of service vulnerability, and CVE-2025-32023 is an out-of-bounds write vulnerability related to the Hyperloglog data structure. Both vulnerabilities could impact the stability and security of Redis instances. The update to redis-6.2.19-1.module+el8.10.0+23330+19e91c41 addresses these issues. The advisory does not provide CVSS scores but rates the impact as important.

CWE-787Out-of-bounds Write (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #5
The product writes data past the end, or before the beginning, of the intended buffer.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
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)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-770Allocation of Resources Without Limits or Throttling (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #25
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
Requirements
Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
Architecture and Design
Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.4 (opens in a new tab)
V13.4.1 (opens in a new tab)
V11.1.4 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Exponential Data Expansion (opens in a new tab)
Serialized Data Parameter Blowup (opens in a new tab)
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Aug 2026, 01:02 UTC

Public exploits and detection1 Exploit-DB entry

WeaknessesCWE-787, CWE-770

Technical details

References

Community reviews

Related threats