NVD / CVE Program· CNA cisa-cg

CVE-2026-81934: Redis TLS pending-data list use-after-free

HighCVSS 7.5 · v4.0—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 30/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.47% (FIRST EPSS).
Someone on the same network segment can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
Fixed version: redis (AlmaLinux:8) 6.2.24-1.module_el8.10.0+4271+7f8f19af; redis-devel (AlmaLinux:8) 6.2.24-1.module_el8.10.0+4271+7f8f19af; redis-doc (AlmaLinux:8) 6.2.24-1.module_el8.10.0+4271+7f8f19af.

Low priority for now. Upgrade to redis (AlmaLinux:8) 6.2.24-1.module_el8.10.0+4271+7f8f19af; redis-devel (AlmaLinux:8) 6.2.24-1.module_el8.10.0+4271+7f8f19af; redis-doc (AlmaLinux:8) 6.2.24-1.module_el8.10.0+4271+7f8f19af or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published: Aug 27, 2026
Updated: Aug 31, 2026
EPSS: 0.4% · 41th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.4%

CISA SSVC decision

Exploitation: proof of concept
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · cisa-cg: 7.1; NVD has not scored this yet; the score shown is the CNA’s.

CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is Redis on your server exposed to the internet?Run a port scan

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Using redis? Add it to your stack and be the first to know about CVEs like this one. (Redis)

Is Redis on your server exposed to the internet?

The free port scanner finds the open ports on your server and matches the service versions it can read against known vulnerabilities. No account needed.

Run a port scan

Versions reported by the vendor

Affected version ranges reported by the assigning authority (cisa-cg). Independent of NVD's CPE analysis and usually ahead of it.

Redis Redis
- 8.2.9, 8.4.6, 8.6.6, 8.8.2, 8.10.1, 7.4.11, 6.2.24, 7.2.16not affected
- before 8.8.2affected
- before 8.2.9affected
- before 8.4.6affected
- before 8.6.6affected
- before 8.10.1affected
- before 7.4.11affected
- before 6.2.24affected
- before 7.2.16affected
Redis Redis Software (Enterprise)
- 8.2.0-46, 8.0.20-96, 7.22.2-179, 7.8.6-303not affected
- before 8.2.0-46affected
- before 8.0.20-96affected
- before 7.22.2-179affected
- before 7.8.6-303affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
AlmaLinux:8	redis	before 6.2.24-1.module_el8.10.0+4271+7f8f19af	6.2.24-1.module_el8.10.0+4271+7f8f19af
AlmaLinux:8	redis-devel	before 6.2.24-1.module_el8.10.0+4271+7f8f19af	6.2.24-1.module_el8.10.0+4271+7f8f19af
AlmaLinux:8	redis-doc	before 6.2.24-1.module_el8.10.0+4271+7f8f19af	6.2.24-1.module_el8.10.0+4271+7f8f19af
AlmaLinux:9	redis	before 6.2.24-1.el9_8	6.2.24-1.el9_8
AlmaLinux:9	redis-devel	before 6.2.24-1.el9_8	6.2.24-1.el9_8
AlmaLinux:9	redis-doc	before 6.2.24-1.el9_8	6.2.24-1.el9_8
Debian:12	redis	before 5:7.0.15-1~deb12u10	5:7.0.15-1~deb12u10
Debian:13	redis	before 5:8.0.2-3+deb13u3	5:8.0.2-3+deb13u3
Debian:14	redis	before 5:8.0.6-3	5:8.0.6-3
Red Hat:enterprise_linux:8::appstream	redis	before 0:6.2.24-1.module+el8.10.0+24746+7b800ac5	0:6.2.24-1.module+el8.10.0+24746+7b800ac5
Red Hat:enterprise_linux:8::appstream	redis-debuginfo	before 0:6.2.24-1.module+el8.10.0+24746+7b800ac5	0:6.2.24-1.module+el8.10.0+24746+7b800ac5
Red Hat:enterprise_linux:8::appstream	redis-debugsource	before 0:6.2.24-1.module+el8.10.0+24746+7b800ac5	0:6.2.24-1.module+el8.10.0+24746+7b800ac5
Red Hat:enterprise_linux:8::appstream	redis-devel	before 0:6.2.24-1.module+el8.10.0+24746+7b800ac5	0:6.2.24-1.module+el8.10.0+24746+7b800ac5
Red Hat:enterprise_linux:8::appstream	redis-doc	before 0:6.2.24-1.module+el8.10.0+24746+7b800ac5	0:6.2.24-1.module+el8.10.0+24746+7b800ac5
Red Hat:enterprise_linux:9::appstream	redis	before 0:7.2.16-1.module+el9.8.0+24745+654dcf03	0:7.2.16-1.module+el9.8.0+24745+654dcf03
Red Hat:enterprise_linux:9::appstream	redis	before 0:6.2.24-1.el9_8	0:6.2.24-1.el9_8
Red Hat:enterprise_linux:9::appstream	redis-debuginfo	before 0:6.2.24-1.el9_8	0:6.2.24-1.el9_8
Red Hat:enterprise_linux:9::appstream	redis-debuginfo	before 0:7.2.16-1.module+el9.8.0+24745+654dcf03	0:7.2.16-1.module+el9.8.0+24745+654dcf03
Red Hat:enterprise_linux:9::appstream	redis-debugsource	before 0:6.2.24-1.el9_8	0:6.2.24-1.el9_8
Red Hat:enterprise_linux:9::appstream	redis-debugsource	before 0:7.2.16-1.module+el9.8.0+24745+654dcf03	0:7.2.16-1.module+el9.8.0+24745+654dcf03
Red Hat:enterprise_linux:9::appstream	redis-devel	before 0:7.2.16-1.module+el9.8.0+24745+654dcf03	0:7.2.16-1.module+el9.8.0+24745+654dcf03
Red Hat:enterprise_linux:9::appstream	redis-devel	before 0:6.2.24-1.el9_8	0:6.2.24-1.el9_8
Red Hat:enterprise_linux:9::appstream	redis-doc	before 0:6.2.24-1.el9_8	0:6.2.24-1.el9_8
Red Hat:enterprise_linux:9::appstream	redis-doc	before 0:7.2.16-1.module+el9.8.0+24745+654dcf03	0:7.2.16-1.module+el9.8.0+24745+654dcf03

+47

Same product

redis: all records

Other highest-scoring records for the same primary product.

CVE-2022-0543It was discovered, that redis, a persistent key-value database, due to a packaging issue, is prone to a (Debian-specific) Lua sandbox…KEV
100Now
CVE-2025-49844Redis Lua Use-After-Free may lead to remote code execution
64This week
CVE-2023-36824Heap overflow in COMMAND GETKEYS and ACL evaluation in Redis
58Plan

Published before and after this one in the same product

← EarlierCVE-2026-23631May 5, 2026 · redis-server Lua use-after-free may allow remote code execution
25Monitor
← EarlierCVE-2026-25243May 5, 2026 · redis-server RESTORE invalid memory access may allow remote code execution
31Monitor
← EarlierCVE-2026-66373Jul 24, 2026 · Redis before 8.8.0, in the unusual case where an authenticated attacker can execute RESTORE, allows remote code execution via a RESTORE…
30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
almalinux:redis	6.2.24-1.module_el8.10.0+4271+7f8f19af · AlmaLinux:8	Package registry (OSV)
almalinux:redis-devel	6.2.24-1.module_el8.10.0+4271+7f8f19af · AlmaLinux:8	Package registry (OSV)
almalinux:redis-doc	6.2.24-1.module_el8.10.0+4271+7f8f19af · AlmaLinux:8	Package registry (OSV)
debian:redis	5:7.0.15-1~deb12u10 · Debian:12	Package registry (OSV)
red hat:redis	0:6.2.24-1.module+el8.10.0+24746+7b800ac5 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:redis-debuginfo	0:6.2.24-1.module+el8.10.0+24746+7b800ac5 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:redis-debugsource	0:6.2.24-1.module+el8.10.0+24746+7b800ac5 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:redis-devel	0:6.2.24-1.module+el8.10.0+24746+7b800ac5 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:redis-doc	0:6.2.24-1.module+el8.10.0+24746+7b800ac5 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
rocky linux:redis	0:6.2.24-1.module+el8.10.0+40313+282db117 · Rocky Linux:8	Package registry (OSV)
suse:redis	7.2.4-150600.3.30.1 · SUSE:Linux Enterprise Server 15 SP6-LTSS	Package registry (OSV)
suse:redis7	7.0.8-150600.8.31.1 · SUSE:Linux Enterprise Server 15 SP6-LTSS	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

redis/rediscommit 6d088c3

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2025-49844328 days apartRedis Lua Use-After-Free may lead to remote code execution
64This week
CVE-2026-23479114 days apartredis-server use-after-free in unblock client flow may allow remote code execution
31Monitor
CVE-2026-23631114 days apartredis-server Lua use-after-free may allow remote code execution
25Monitor

Bug bounty scope

Redis VDPHackerOne · disclosure only (VDP)

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Not on record for this CVE: researcher credit.

Technical details

Attack conditions

Someone on the same network segment can trigger it.
A low-privileged account is enough.
No user action is required.
Special conditions such as timing or configuration are required.

If successful

Confidentiality
Integrity
Availability

Attack vector: Adjacent
Attack complexity: High
Privileges required: Low
User interaction: None
Scope: X

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log (1)

Fix✗ → ✓Sep 28, 2026, 10:47 PM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/redis/redis/commit/6d088c335d5c3ec49a6c28486140b498e70b7834

Show all references (19 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records