CVE-2026-81934
Redis TLS pending-data list use-after-free
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 8.8.2, 8.2.9, 8.4.6, 8.6.6, 8.10.1, and 7 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: poc
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Redis Redis
fixed in 8.8.2; fixed in 8.2.9; fixed in 8.4.6; fixed in 8.6.6; fixed in 8.10.1; fixed in 7.4.11; fixed in 6.2.24; fixed in 7.2.16
- Redis Redis Software (Enterprise)
fixed in 8.2.0-46; fixed in 8.0.20-96; fixed in 7.22.2-179; fixed in 7.8.6-303
References 24
GitHub · redis/redis
GitHub · v12-security/pocs
raw.githubusercontent.com
- redis/redis/8.2/00-RELEASENOTES
- redis/redis/8.4/00-RELEASENOTES
- redis/redis/8.6/00-RELEASENOTES
- redis/redis/8.8/00-RELEASENOTES
- redis/redis/8.10/00-RELEASENOTES
- cisagov/CSAF/develop/csaf_files/IT/white/2025/va-26-239-01.json
- redis/redis/7.4/00-RELEASENOTES
- redis/redis/7.2/00-RELEASENOTES
- redis/redis/6.2/00-RELEASENOTES