Skip to main content

Redis CVE-2026-81934

| EUVDEUVD-2026-67227 HIGH
Use After Free (CWE-416)
2026-08-27 cisa-cg GHSA-32xw-c2hw-m34g
Use After Free Memory Corruption Redis Red Hat Suse
7.5
CVSS 4.0 · Vendor: cisa-cg
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify TLS-enabled Redis listener on adjacent network
  2. Delivery
    Establish TLS client connection
  3. Exploit
    Send crafted multi-command sequence
  4. Execution
    Trigger peer connection teardown mid-processing
  5. Persist
    Dereference freed TLS pending-data list entry (UAF)
  6. Impact
    Execute arbitrary commands as Redis server process

Vulnerability Assessment

Weakness
CWE
CWE-416
ASVS 5.0
V15 - Secure Coding and Architecture Memory lifecycle management
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Sign in to read
Exploitation Conditions

Exploitation requires that Redis be explicitly configured with TLS support - the tls-port directive must be set (and optionally tls-replication yes for replica paths); TLS is disabled in Redis default configurations, so out-of-the-box deployments are not affected. The CVSS 4.0 official vector specifies AV:A (adjacent network) and AT:P (specific attack preconditions present), meaning the attacker must be network-adjacent to the Redis listener and must engineer a specific connection-state sequence where one command causes a peer connection to be closed while that connection's data remains on the pending-data list. The CVSS 4.0 vector lists PR:L (low privileges required), which conflicts with the CVE description's 'unauthenticated' characterization - authentication requirements are not independently confirmed and should be verified with the vendor. Exploitation is further constrained by AC:H, consistent with SSVC's 'Automatable: no' finding; attackers cannot simply fire a single packet but must orchestrate a multi-step interaction. Plain TCP Redis instances (no TLS) are not affected by this specific flaw.
Impact

The official CVSS 4.0 vector scores this at 7.5 with AV:A (adjacent network), AC:H, AT:P, and PR:L - indicating high attack complexity, specific preconditions, and low-privilege requirement. This stands in notable tension with the CVE description's characterization of the attacker as 'remote, unauthenticated': the adjacent-network and low-privilege ratings are stricter than the description implies, and defenders should verify authentication requirements directly with the Redis security team before assuming either framing is authoritative. SSVC's 'Automatable: no' rating reinforces the AC:H signal - reliable exploitation requires stateful, non-trivial interaction, which suppresses broad spray-and-pray attacks. EPSS at 0.58% (45th percentile) confirms that despite a public POC, exploitation has not proliferated widely. The combination of non-automatable exploitation and a non-default TLS precondition meaningfully narrows the realistic threat population compared to the raw CVSS headline. That said, SSVC's 'Technical Impact: total' and the availability of public exploit code mean that any TLS-enabled Redis deployment exposed beyond strictly trusted network segments warrants priority patching - the blast radius if successfully exploited is full server compromise. The vulnerability is not yet in CISA KEV, though the CSAF advisory was filed by cisa-cg.
Exploit ScenarioDerived

An attacker with adjacent network access to a TLS-enabled Redis instance establishes a TLS client connection and sends a crafted sequence of commands engineered to cause one connection to be torn down while its data object remains referenced in the TLS pending-data list; when Redis next processes that list, it dereferences the freed memory. A public POC exists, though SSVC rates the technique non-automatable, indicating the exploit requires deliberate state manipulation rather than a simple single-packet trigger, making mass exploitation less likely but targeted compromise feasible.
This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
1 public PoC Patch available 0.6% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv2 – Aug 31, 2026

Use-after-free in Redis's TLS pending-data handler (tlsProcessPendingData()) enables remote attackers to potentially execute arbitrary commands at the privilege level of the Redis server process. The flaw spans all major active Redis release lines and is confirmed fixed in versions 6.2.24, 7.2.16, 7.4.11, 8.2.9, 8.4.6, 8.6.6, 8.8.2, and 8.10.1 - exploitation is gated on TLS being explicitly configured, which is non-default. A public proof-of-concept exists; SSVC rates technical impact as total but automation as not feasible, and the vulnerability is not currently listed in CISA KEV.

Earlier versions of this analysis (1)
v1 Aug 27, 2026 - 20:33 CVSS 9.2

Remote code execution in Redis affects deployments built with TLS support, where a use-after-free in the tlsProcessPendingData() function lets a remote, unauthenticated attacker corrupt memory and run arbitrary commands with the privileges of the Redis server process. Publicly available exploit code exists (v12-security PoC), and the CVSS 4.0 base score is 9.2, though the vector's Attack Requirements flag (AT:P) indicates exploitation is not fully deterministic. It is fixed in Redis 8.2.9, 8.4.6, 8.6.6, 8.8.2, and 8.10.1.

RemediationAI

Upgrade to the patched release corresponding to your Redis branch: 6.2.24, 7.2.16, 7.4.11, 8.2.9, 8.4.6, 8.6.6, 8.8.2, or 8.10.1, available via the Redis GitHub releases page (e.g., https://github.com/redis/redis/releases/tag/8.10.1). Redis Enterprise customers should apply the patches documented in rs-7-8-6-303 (https://redis.io/docs/latest/operate/rs/release-notes/rs-7-8-releases/rs-7-8-6-303/), rs-7-22-2-179, and rs-8-0-20-96 as appropriate for their deployment. As an interim compensating control, disabling TLS on Redis (tls-port 0, removing tls-replication yes) eliminates the attack surface entirely since the vulnerable code path is unreachable without TLS - the trade-off is loss of encryption in transit and potential compliance violations. Restricting Redis network access to trusted client hosts via firewall rules or network segmentation reduces exposure for adjacent-network attack vectors but does not eliminate risk if the attacker already has network adjacency. A CISA CSAF advisory is available at https://raw.githubusercontent.com/cisagov/CSAF/develop/csaf_files/IT/white/2025/va-26-239-01.json.

Affected VersionsENISA

Redis 8.8.0

Affected Packages

euvd redis no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Sign in to check
Technical ContextAI · show details

Redis is an open-source in-memory data structure store widely used as a cache, session store, and message broker. The affected function tlsProcessPendingData() manages a queue of pending TLS data for active client connections. CWE-416 (Use After Free) arises here when a command execution path causes one connection to be closed and freed while a pointer to that connection's data remains live in the TLS pending-data list; subsequent processing of that list dereferences freed memory, producing memory corruption. The Redis 6.2.24 release notes explicitly confirm the root cause: 'Use-after-free in the TLS pending-data list when a command closes another pending connection.' The CPE string cpe:2.3:a:redis:redis:*:*:*:*:*:*:*:* covers all versions of the Redis core package across all platforms. Memory corruption of this class can be leveraged for arbitrary code execution, though reliable exploitation typically requires careful timing to win the race between deallocation and dereference.

Know when Redis gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources
Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

Vendor (cisa-cg) PRIMARY 7.5 CRITICAL
CVSS:4.0/AV:A/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
vuln.today AI 8.1 HIGH

Description states remote unauthenticated access (AV:N, PR:N); AC:H reflects the non-automatable, stateful UAF trigger requiring specific connection-state timing.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE HIGH
Red Hat 7.5 HIGH

Primary rating from Vendor (cisa-cg).

CVSS VectorVendor: cisa-cg

Attack Vector
Adjacent
Attack Complexity
High
Attack Requirements
Present
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

3
Severity Changed
Aug 31, 2026 - 20:22 NVD
CRITICAL HIGH
CVSS changed
Aug 31, 2026 - 20:22 NVD
9.2 (CRITICAL) 7.5 (HIGH)
CVE Published
Aug 27, 2026 - 19:40 cve.org
CRITICAL 9.2

DescriptionCVE.org

Redis contains a use-after-free vulnerability in the 'tlsProcessPendingData()' function, which handles the TLS pending-data list if Redis is configured with TLS support. A remote, unauthenticated attacker may be able to execute arbitrary commands with the privileges of the Redis server. Fixed in Redis 8.2.9, 8.4.6, 8.6.6, 8.8.2, and 8.10.1.

Articles & Coverage 1

News Critical RCE in Redis TLS (tlsProcessPendingData UAF) - CVE-2026-81934 Aug 27, 2026

Technical POC Analysis

This is a heap use-after-free, CWE-416, in tlsProcessPendingData() in src/tls.c.

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Sign in to read

Latest POC

1 public PoC link from github

Sign in to open the public PoC links collected for this CVE.

Sign in to read

Executive ViewAI

Why It Matters

CVE-2026-81934 affects Redis implementations with TLS enabled, allowing attackers to execute commands with Redis server privileges and potentially compromise stored data. Publicly available exploit code exists, and the vulnerability spans all major Redis versions, creating organizational risk where TLS-protected instances are deployed.

Business Impact: High
Compensating Controls

Apply vendor patch. Interim mitigations if immediate patching is not possible: disable TLS connections (if operationally acceptable), restrict network access to Redis instances via firewall, and enable Redis command logging to detect exploitation attempts.

Threat Intelligence Overview

EPSS Score
0.6%
Top 55% exploitable
Prevalence
High
widely deployed caching and session store across cloud and enterprise environments
Social Media
2
Sightings
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment Vendor CIRCL GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 0.6%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
Poc
System Exposure· derived
Controlled
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

59
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +38
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Use After Free HIGH

Use-after-free vulnerabilities occur when a program continues to access memory through a pointer after that memory has been deallocated.

Memory Corruption HIGH

Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.

More in Redis

View all
CVE-2026-48172 CRITICAL POC
10.0 May 21

Privilege escalation to root in the LiteSpeed User-End cPanel Plugin (versions 2.3 through before 2.4.5) lets attackers

CVE-2025-49844 CRITICAL POC
9.9 Oct 03

UAF in Redis 8.2.1 via crafted Lua scripts by authenticated users. EPSS 12.4%. Patch available.
CVE-2022-0543 CRITICAL POC
10.0 Feb 18

It was discovered, that redis, a persistent key-value database, due to a packaging issue, is prone to a (Debian-specific
CVE-2018-11218 CRITICAL POC
9.8 Jun 17

Memory Corruption was discovered in the cmsgpack library in the Lua subsystem in Redis before 3.2.12, 4.x before 4.0.10,
CVE-2025-46817 HIGH POC
7.0 Oct 03

Redis is an open source, in-memory database that persists on disk. Versions 8.2.1 and below allow an authenticated user

CVE-2015-4335 CRITICAL POC
10.0 Jun 09

Redis before 2.8.21 and 3.x before 3.0.2 allows remote attackers to execute arbitrary Lua bytecode via the eval command.
CVE-2016-8339 CRITICAL POC
9.8 Oct 28

A buffer overflow in Redis 3.2.x prior to 3.2.4 causes arbitrary code execution when a crafted command is sent. Rated cr
CVE-2026-77602 CRITICAL POC
9.9 Sep 23

Authenticated remote code execution in OpenC3 COSMOS (Ruby gem 'openc3' versions 5.1.0 through 7.2.1) lets any logged-in
CVE-2026-27574 CRITICAL POC
9.9 Feb 21

Code injection in OneUptime monitoring via custom JS monitor using vm module. PoC and patch available.
CVE-2026-84372 CRITICAL POC
9.8 Sep 01

RESP protocol command injection in Predis, the popular PHP client for Redis and Valkey, affects versions 3.0.0-RC1 throu
CVE-2021-31649 CRITICAL POC
9.8 Jun 24

In applications using jfinal 4.9.08 and below, there is a deserialization vulnerability when using redis,may be vulnerab
CVE-2020-11981 CRITICAL POC
9.8 Jul 17

An issue was found in Apache Airflow versions 1.10.10 and below. Rated critical severity (CVSS 9.8), this vulnerability

Same weakness CWE-416 – Use After Free

View all
CVE-2019-0708 CRITICAL POC
9.8
CVE-2015-5119 CRITICAL POC
9.8
CVE-2014-0322 HIGH POC
8.8
CVE-2012-4792 HIGH POC
8.8
CVE-2009-4324 HIGH POC
7.8
CVE-2015-0313 CRITICAL POC
9.8
CVE-2015-5122 CRITICAL POC
9.8
CVE-2013-2551 HIGH POC
8.8

Same technique Use After Free

View all
CVE-2012-4969 HIGH POC
8.1

Vendor StatusVendor

SUSE

Severity: Important
Product Status
SUSE Linux Enterprise Module for Server Applications 15 SP7 Not-Affected
SUSE Linux Enterprise Server 15 SP7 Not-Affected
SUSE Linux Enterprise Server 16.0 Not-Affected
SUSE Linux Enterprise Server 16.1 Not-Affected
SUSE Linux Enterprise Server for SAP Applications 15 SP7 Not-Affected

References

Advisories & patches
PATCH https://github.com/redis/redis/commit/6d088c335d5c3ec49a6c28486140b498e70b7834 ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2026-81934 ADVISORY https://vuldb.com/vuln/396400 REF https://github.com/redis/redis/releases/tag/6.2.24 REF https://github.com/redis/redis/releases/tag/7.2.16 REF https://github.com/redis/redis/releases/tag/7.4.11 REF https://github.com/redis/redis/releases/tag/8.10.1 REF https://github.com/redis/redis/releases/tag/8.2.9 REF https://github.com/redis/redis/releases/tag/8.4.6 REF https://github.com/redis/redis/releases/tag/8.6.6 REF https://github.com/redis/redis/releases/tag/8.8.2 REF https://raw.githubusercontent.com/cisagov/CSAF/develop/csaf_files/IT/white/2025/va-26-239-01.json REF https://raw.githubusercontent.com/redis/redis/6.2/00-RELEASENOTES REF https://raw.githubusercontent.com/redis/redis/7.2/00-RELEASENOTES REF https://raw.githubusercontent.com/redis/redis/7.4/00-RELEASENOTES REF https://raw.githubusercontent.com/redis/redis/8.10/00-RELEASENOTES REF https://raw.githubusercontent.com/redis/redis/8.2/00-RELEASENOTES REF https://raw.githubusercontent.com/redis/redis/8.4/00-RELEASENOTES REF https://raw.githubusercontent.com/redis/redis/8.6/00-RELEASENOTES REF https://raw.githubusercontent.com/redis/redis/8.8/00-RELEASENOTES REF https://redis.io/docs/latest/operate/rs/release-notes/rs-7-22-releases/rs-7-22-2-179/ REF https://redis.io/docs/latest/operate/rs/release-notes/rs-7-8-releases/rs-7-8-6-303/ REF https://redis.io/docs/latest/operate/rs/release-notes/rs-8-0-releases/rs-8-0-20-96/ REF https://redis.io/docs/latest/operate/rs/release-notes/rs-8-2-releases/rs-8-2-0-46/ REF https://www.cve.org/CVERecord?id=CVE-2026-81934

Search Externally

GitHub PoC Exploit-DB PacketStorm Snyk Rapid7 Nuclei Templates Trickest PoC
Back

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy