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.
CVE-2026-81934
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-27. a secondary CVSS source baseline 9.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(high)
- EG Risk
- 60(Track*)EG Risk 60/100SSVC: Track*
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity98% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- 1%
- EPSS %ILE
- 45%
- KEV
- Not listed
Published
August 27, 2026
Last Modified
August 28, 2026
Advisory Details (7)
Auto-updated Aug 28, 2026pocs/redis/server_ssl at main · v12-security/pocs · GitHub
https://github.com/v12-security/pocs/tree/main/redis/server_sslcommit 6d088c335d5c (redis/redis)
Patch available: redis/redis 8.8.2 (contains commit 6d088c335d5c)
https://github.com/redis/redis/commit/6d088c335d5c3ec49a6c28486140b498e70b7834Vendor Advisories for CVE-2026-81934(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 26× in last 7d / 26× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 03:02 UTCEG score recompute
- 2026-08-30 03:02 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 23:10 UTCGHSA enrichment
- 2026-08-29 19:18 UTCGHSA enrichment
- 2026-08-29 15:24 UTCGHSA enrichment
- 2026-08-29 11:31 UTCGHSA enrichment
- 2026-08-29 07:38 UTCGHSA enrichment
- 2026-08-29 03:44 UTCGHSA enrichment
- 2026-08-28 23:53 UTCEG score recompute
- 2026-08-28 23:52 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 16:40 UTCEG score recompute
- 2026-08-28 16:40 UTCGHSA enrichment
- 2026-08-28 15:52 UTCEG score recompute
- 2026-08-28 15:51 UTCGHSA enrichment
- 2026-08-28 15:42 UTCEG score recompute
- 2026-08-28 15:41 UTCGHSA enrichment
- 2026-08-28 11:55 UTCGHSA enrichment
- 2026-08-28 08:04 UTCGHSA enrichment
- 2026-08-28 04:12 UTCGHSA enrichment
- 2026-08-28 00:21 UTCEG score recompute
- 2026-08-28 00:20 UTCGHSA enrichment
- 2026-08-27 20:26 UTCEG score recompute
- 2026-08-27 20:14 UTCEG score recompute
Show 1 moreShow fewer
- 2026-08-27 20:13 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-81934?
When was CVE-2026-81934 disclosed?
Is CVE-2026-81934 actively exploited?
What is the CVSS score of CVE-2026-81934?
How do I remediate CVE-2026-81934?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-81934
Is Your Infrastructure Affected by CVE-2026-81934?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.