Redis Patch Bypass Enables Multiple RCE Exploits as PoCs for TLS and Stream Vulnerabilities Go Public
Redis has suffered a rapid series of remote code execution vulnerabilities over the past month, with the latest TLS pending list flaw (QVD-2026-58458) now accompanied by public technical details and a working proof-of-concept. Security researchers have already reproduced the issue, and the vendor released an emergency fix. Because Redis is ubiquitous in backend architectures for caching, sessions, message queues, and leaderboards, any vulnerability in the service immediately affects a wide range of organizations.
The most concerning disclosure is the July patch-bypass vulnerability targeting CVE-2026-25243. The original fix addressed a reference-counting problem with shared NACK objects in stream consumer groups, yet the remediation was incomplete. Attackers can chain the commands XGROUP, EVAL, and RESTORE to trigger a Double Free memory corruption primitive, ultimately achieving arbitrary code execution on the server. Patch-bypass issues are particularly dangerous because they target teams that believe they have already mitigated the risk after applying the initial update.
The affected versions for the bypass are Redis 6.2.22 and earlier, 7.4.9 and earlier, and 8.6.4 and earlier; the official remediation begins at version 8.8.0. The August 26 disclosure of QVD-2026-58458 similarly provides a public PoC, lowering the barrier for exploitation to the level of script kiddies copying existing code. Although all three vulnerabilities require authentication, real-world deployments frequently use weak passwords, empty passwords, or publicly reachable instances, rendering the authentication requirement ineffective against automated scanners.
Once an attacker gains control, the consequences extend far beyond data leakage. Redis instances often sit at the center of internal networks; code execution allows attackers to harvest credentials, map internal assets, and pivot to databases and application servers. The following practical steps are recommended for defenders:
- Perform a complete asset inventory covering production, test, and shadow instances, then upgrade every affected version to the latest patched release.
- Enforce strict network controls so that Redis is never exposed to the public internet and is reachable only from explicitly allowed internal IPs; immediately remediate weak or missing passwords via requirepass or ACLs.
- Enable logging and audit for high-risk command sequences, especially non-standard usage of XGROUP, EVAL, and RESTORE; restrict Lua script execution via ACLs when not required.
- Update container base images in addition to host-level patches to avoid version drift between the running container and the patched host.
- Incorporate official Redis security announcements and threat-intelligence feeds into routine monitoring processes.
This wave of vulnerabilities underscores that the security posture of foundational infrastructure components directly determines the resilience of the entire environment. With public PoCs, patch bypasses, and near-universal version coverage, the race is now between rapid remediation and automated scanning campaigns.
Related articles
Zero-Day Vulnerabilities: The Invisible Threats Lurking in Modern Software
Zero-Day vulnerabilities represent one of the most challenging problems in cybersecurity because developers have no time to prepare defenses before exploitation begins. These flaws exist in software components without the knowledge of vendors, leaving antivirus tools and existing security mechanisms unable to detect attacks. Researchers discover such issues through techniques including fuzzing, reverse engineering, and static analysis. High-profile examples such as Heartbleed in OpenSSL, EternalBlue in Windows SMB, and Log4Shell in the Log4j library illustrate how single errors can affect millions of systems worldwide. Bug Bounty programs now allow companies to harness independent researchers to find problems before criminals exploit them. Organizations can reduce risk through regular updates, least-privilege principles, multi-factor authentication, and layered defenses, though complete elimination of zero-day risk remains impossible.
11-Year-Old Linux Kernel Race Condition NoisyTCP (CVE-2026-99288) Enables Remote DoS on Nginx, Apache and SSH Servers
Security researcher Hyunwoo Kim disclosed NoisyTCP (CVE-2026-99288), an 11-year-old race condition in the Linux kernel networking stack that allows unauthenticated remote attackers to trigger kernel panics and crash servers. The flaw stems from concurrent access to the ehash table during TCP socket lookup, where one CPU context may dereference a freed request_sock or full socket while another reuses the memory via SYN cookies. Exploitation requires multiple RX queues or RPS enabled and succeeds reliably on virtualized environments within seconds to minutes. Affected systems include nearly all distributions running kernels from 4.4 onward until the fix landed in November 2026. Temporary mitigations involve disabling SYN cookies or restricting traffic to a single RX queue, though both reduce resilience or performance. The researcher published full technical details on GitHub after coordinated disclosure.
Check Point Gateways Hit by PHP2Shell Exploits Installing TSGA Backdoor via Chained CVEs
An unidentified threat actor has been actively exploiting known vulnerabilities in unpatched Check Point Security Gateways to deploy the TSGA backdoor. The campaign began on 30 October 2026 against Israeli organizations and expanded on 2 November to targets across multiple countries and industries. Initial access leveraged CVE-2026-109618 and CVE-2026-109619 in exposed Mobile Access portals, followed by local privilege escalation through the previously unknown CVE-2026-123039 in Gaia OS. Attackers then installed PHP web shells and the TSGA backdoor, which provides encrypted remote access, configuration theft, persistence mechanisms, and log tampering via the embedded TSProxy component. In the first wave, operators pivoted to VMware ESXi hosts and deployed the destructive wiper destroy_v6. While tooling overlaps with the China-linked Armory Castle group’s PhiliKit framework, the use of a wiper and references to the Israel-Palestine conflict leave attribution open to three scenarios.
Apache Shiro Authentication Bypass Vulnerability Disclosed, Fixed in August Update
A critical authentication bypass vulnerability has been identified in the Java security framework Apache Shiro under specific LDAP caching configurations. The flaw, tracked as CVE-2026-129349, affects versions prior to 3.0.0 and carries a CVSSv4.0 base score of 9.1, rated Critical. Once a valid user authenticates successfully, subsequent login attempts using the cache accept any password for that username, enabling impersonation attacks. The Apache Shiro development team disclosed the issue on November 14, 2026, noting that the vulnerability was already resolved in version 3.0.1 released in August 2026. Version 3.0.2 was made available on November 8, 2026, and users are urged to upgrade immediately to the latest release.