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

> Remote unauthenticated attackers can execute arbitrary code on Redis servers configured with TLS due to a use-after-free vulnerability.

- **Severity:** High 7.5 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** AZL-98240, BELL-CVE-2026-81934, CLSA-2026-1789377770, CLSA-2026-1789395343, DEBIAN-CVE-2026-81934, GHSA-32xw-c2hw-m34g, SUSE-SU-2026:3990-1, SUSE-SU-2026:3991-1, SUSE-SU-2026:4068-1, SUSE-SU-2026:4069-1, UBUNTU-CVE-2026-81934

## What is CVE-2026-81934?

CVE-2026-81934 is a high-severity use after free vulnerability in Redis, published on 27 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2026-81934?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `redis` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 6.2.6-150400.3.52.1 |
| `redis` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 6.2.6-150400.3.52.1 |
| `redis` | SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 6.2.6-150400.3.52.1 |
| `redis7` | SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 7.0.8-150500.3.37.1 |
| `redis` | SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 6.2.6-150400.3.52.1 |
| `redis7` | SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 7.0.8-150500.3.37.1 |
| `redis` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 6.2.6-150400.3.52.1 |
| `redis` | SUSE:Linux Enterprise Server 15 SP5-LTSS | All versions | 6.2.6-150400.3.52.1 |
| `redis7` | SUSE:Linux Enterprise Server 15 SP5-LTSS | All versions | 7.0.8-150500.3.37.1 |
| `redis` | SUSE:Linux Enterprise Server 15 SP6-LTSS | All versions | 7.2.4-150600.3.30.1 |
| `redis7` | SUSE:Linux Enterprise Server 15 SP6-LTSS | All versions | 7.0.8-150600.8.31.1 |
| `redis` | SUSE:Linux Enterprise Server for SAP Applications 15 SP4 | All versions | 6.2.6-150400.3.52.1 |
| `redis` | SUSE:Linux Enterprise Server for SAP Applications 15 SP5 | All versions | 6.2.6-150400.3.52.1 |
| `redis7` | SUSE:Linux Enterprise Server for SAP Applications 15 SP5 | All versions | 7.0.8-150500.3.37.1 |
| `redis` | SUSE:Linux Enterprise Server for SAP Applications 15 SP6 | All versions | 7.2.4-150600.3.30.1 |
| `redis7` | SUSE:Linux Enterprise Server for SAP Applications 15 SP6 | All versions | 7.0.8-150600.8.31.1 |

## How do I fix CVE-2026-81934?

Apply the vendor's patch.

## Is CVE-2026-81934 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-81934 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-81934 and fix it if it is affected.

What it is: CVE-2026-81934 is a high-severity use after free vulnerability in Redis, published on 27 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-81934 exists.

Affected product: Redis. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-81934/ (Markdown: https://insights.sbomify.com/CVE-2026-81934/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-81934
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-81934
- OSV: https://osv.dev/vulnerability/CVE-2026-81934

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-81934/
Summaries are generated and may contain mistakes; the official description above is the record.