CVE Tools
Track your stack

CVE-2026-81934

Redis TLS pending-data list use-after-free

No known exploitation. EPSS puts it in the 40th percentile. Fixed versions are out.

CVSS 3.17.1HighEPSS percentile40th0.5% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix2 products8 fixed builds listed below

Published Updated Sources: CVE.org, NVD, CSAF

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • RedisAffected: < 8.8.2Upgrade to: 8.8.2Affected: < 8.2.9Upgrade to: 8.2.9Affected: < 8.4.6Upgrade to: 8.4.6Affected: < 8.6.6Upgrade to: 8.6.6 + 4 more branchesStated by: CVE record
  • Redis SoftwareAffected: < 8.2.0-46Upgrade to: 8.2.0-46Affected: < 8.0.20-96Upgrade to: 8.0.20-96Affected: < 7.22.2-179Upgrade to: 7.22.2-179Affected: < 7.8.6-303Upgrade to: 7.8.6-303Stated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

Check it yourselfA free OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

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.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS40th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.5% chance of exploitation activity in the next 30 days, which ranks it in the 40th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

11 events over 9 days, from the signal feeds we watch.

  1. OpenVAS check added
  2. Patch availablerecord updated
  3. Patch availablepatch available, record updated, record updated
  4. Publishedweakness classified, att&ck mapped, record updated

Affected products

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

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

Scored 7.1 by NVD.

How it is reached

  • Attack Vector AdjacentRequires access to the local network (e.g. same Wi-Fi, Bluetooth)
  • Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
  • Privileges Required LowRequires basic user-level privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

References in the record

And 21 more references. See all after sign-in

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Redis, not every advisory.