CyberSecBulletin
CVE-2026-81934NVD status: Awaiting Analysis

Redis: Use After Free

Published Updated By the CyberSecBulletin desk

CVE-2026-81934 is a high-severity use after free vulnerability in Redis, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited from the same local network by an attacker with a low-privileged account, without any action from a user. The record lists versions 8.8.2, 8.2.9, 8.4.6 as the first without the flaw, so updating Redis to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.48% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Redis to 8.8.2 or 8.2.9 or 8.4.6 or 8.6.6, whichever matches your release line, or a later version.
  2. Update Redis Software (Enterprise) to 8.2.0-46 or 8.0.20-96 or 7.22.2-179 or 7.8.6-303, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
RedisRedisbefore 8.8.2; before 8.2.9; before 8.4.6; before 8.6.6; before 8.10.1; before 7.4.11; before 6.2.24; before 7.2.168.8.2, 8.2.9, 8.4.6, 8.6.6, 8.10.1, 7.4.11
RedisRedis Software (Enterprise)before 8.2.0-46; before 8.0.20-96; before 7.22.2-179; before 7.8.6-3038.2.0-46, 8.0.20-96, 7.22.2-179, 7.8.6-303

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
AdjacentThe attacker must be on the same local network segment.
Attack complexity
HighSuccess depends on conditions outside the attacker's control.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA.

Scoring systemScoreSeverityScored by
CVSS 4.07.5HighCNA
CVSS 3.17.1HighCNA

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Use After Free

The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

How developers prevent this class of flaw

  • Choose a language that provides automatic memory management.
  • When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.

More Use After Free vulnerabilities (CWE-416)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Redis

All Redis vulnerabilities

Recent Use After Free vulnerabilities

Spotted an error? Tell us.