High [CVE-2026-81934] Arbitrary code execution via TLS pending-data list use-after-free
This high-severity Red Hat Linux advisory covers CVE-2026-81934 affecting Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9, Red Hat package: redis.
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
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.
A flaw was found in Redis. This is an Important flaw in Redis, enabling remote, unauthenticated attackers to achieve arbitrary code execution.
The vulnerability specifically impacts Redis instances configured with TLS support, which is not enabled by default in Red Hat Enterprise Linux, thereby limiting exposure in standard deployments. Red Hat severity: Important — CVSS 7.5 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H).
Weakness: CWE-416. Affected Red Hat products: Red Hat Enterprise Linux 8; Red Hat Enterprise Linux 9.
Red Hat lists Red Hat Hardened Images as not affected. Red Hat does not currently list a fixing RHSA for this CVE.
Affected products named by the advisory: Red Hat package: redis.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 2 hours ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 2 hours ago·verify at source
Mitigation checklist
- For Redis instances where TLS is enabled, consider disabling TLS if it is not strictly required. Alternatively, restrict network access to the Redis server to trusted clients only, using firewall rules or network access controls, to prevent unauthenticated remote attackers from reaching the vulnerable service. If TLS is enabled, a restart of the Redis service may be required for changes to take effect.
Official advisory · high-confidence parse· fetched 2 hours ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.