CVE-2026-81934: Redis Vulnerability in TLS Data Processing
This text was generated using artificial intelligence (AI).On August 27, 2026, CVE-2026-81934 released for Redis. The vulnerability affects the function tlsProcessPendingData, which processes the list of pending TLS data, provided that Redis is configured with TLS support. The CVSS score is 9.8 (critical).
An unauthenticated attacker may be able to execute arbitrary commands over the network with the privileges of the Redis server. Therefore, Redis instances configured with TLS are particularly relevant for prioritization.
CVE-2026-81934 is a use-after-free vulnerability in tlsProcessPendingData. The function processes pending TLS data from a Redis instance.
The documented potential impact is the execution of arbitrary commands within the Redis server's authorization context. The TLS configuration is a prerequisite for the vulnerability described.
For organizations in Germany and Austria that fall under NIS-2 or the Austrian NISG, respectively, the exploitation of such a vulnerability may trigger reporting obligations. Companies based in Switzerland are subject to the revised Information Security Act (ISG), which requires reporting to BACS. Furthermore, in the event of a security incident involving personal data in the EU, the 72-hour reporting requirement under GDPR Article 33 applies. Operators of critical infrastructure should therefore treat the patch status of Redis instances with TLS configuration as a high priority.
Revised Redis Releases
Fixed releases for CVE-2026-81934 are available for several Redis branches:
Redis 8.2.9
Redis 8.4.6
Redis 8.6.6
Redis 8.8.2
Redis 8.10.1
Organizations should check the patch status and vulnerability status of their Redis instances. Systems with TLS configuration should be prioritized.
Risk Mitigation Measures
The following steps are based on the documented vulnerability and the provided fixes:
Identify Redis instances with TLS configuration.
Check for a patch and determine whether CVE-2026-81934 affects your system.
Update affected systems running on Redis 8.2.9, 8.4.6, 8.6.6, 8.8.2, or 8.10.1, depending on the branch used.
Do not expose Redis instances without authentication or network segmentation.
Establish continuous vulnerability and vendor risk monitoring.
Verifying authentication and network segmentation complements the process of updating the affected Redis instances. Both measures address the availability of a service, while the patch status addresses the technical vulnerability in the Redis branch being used.
Visibility of Redis Services
LocateRisk EASM can identify Redis instances among enterprise assets and highlight accessible services for technical prioritization. For CVE-2026-81934, the combination of the Redis service, TLS configuration, and accessibility is relevant. In addition to actively used systems, the continuous external perspective also captures forgotten or uninventoried instances—such as those from shadow IT or discontinued projects—that are often not tracked in internal asset management.
However, the presence of a visible Redis instance does not prove that a specifically vulnerable version is in use. Therefore, assessing CVE-2026-81934 requires checking the patch status as well as verifying the TLS configuration, authentication, and network segmentation.
Am I affected?
Redis is affected; the vulnerability has been fixed in versions 8.2.9, 8.4.6, 8.6.6, 8.8.2, and 8.10.1. If you want to know whether Redis is even visible from the outside in your own infrastructure, you can use the CVE Quick Check Use the tool at the end of this article: It shows exposed systems and the software that is visible from the outside.
It is not always possible to determine the specific version that has been installed from the outside—the key factor is comparing it with the manufacturer's advisory.
CVE-2026-81934 is a use-after-free vulnerability in the Redis function tlsProcessPendingData, which processes outbound TLS data. It allows an unauthenticated attacker on the network to potentially execute arbitrary commands with the privileges of the Redis server. The CVSS score is 9.8 (critical).
This vulnerability affects Redis instances that are configured with TLS support. Systems without TLS configuration are not affected by this vulnerability.
Fixed releases are available for several branches: Redis 8.2.9, 8.4.6, 8.6.6, 8.8.2, and 8.10.1. Administrators should identify the Redis version they are using and update it to the appropriate patched release.
As of August 28, 2026. This article is intended for general informational purposes only and does not constitute legal, security, or operational advice in specific cases. The security situation and patch availability may have changed since this was published; the linked vendor advisory is always authoritative. Despite careful research, we do not guarantee that the information is up-to-date, accurate, or complete.
CVE Quick Check
In just a few minutes, check whether there are any indications of a current CVE on your externally visible attack surface.
A rough estimate in just a few minutes via email.
Learn more during a free consultation with a LocateRisk consultant.
You'll receive this by email
companyYour Company, LLC
Verified CVECVE-2024-3094
Passive Assessment
Information About the CVENotes found
Want to find out more, book a demo or simply exchange ideas? We look forward to hearing from you!
We use cookies to optimize our website and our service.
Functional
Always active
Technical storage or access is strictly necessary for the lawful purpose of enabling the use of a particular service expressly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a message over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that have not been requested by the subscriber or user.
Statistics
The technical storage or access, which is carried out exclusively for statistical purposes.Technical storage or access used solely for anonymous statistical purposes. Without a subpoena, the voluntary consent of your Internet service provider, or additional records from third parties, information stored or accessed for this purpose alone generally cannot be used to identify you.
Marketing
Technical storage or access is necessary to create user profiles, to send advertisements, or to track the user on a website or across multiple websites for similar marketing purposes.
English 
Deutsch 
Français