Zapscape Flaw in KVM Breaks Nested Virtualization Isolation Allowing L1 Guest Root Code Execution on Linux Host
A security flaw in KVM/x86 within the Linux kernel has highlighted a risk that many infrastructure platforms accept almost without question: nested virtualization exposed to untrusted workloads. The vulnerability, named Zapscape and registered as CVE-2026-64561, can allow an attacker with kernel privileges inside a level-1 virtual machine to execute code on the host with root permissions.
The problem centers on the shadow MMU and the way KVM manages shadow page tables when the L1 guest itself acts as a hypervisor for an L2 guest. In practical terms, the isolation that normally protects the host from activity inside a VM is weakened exactly in the scenario where a provider grants more power to a tenant by allowing nested virtualization inside the tenant’s own VM.
The technical root cause lies in an incorrect ordering when checking a “stale root” condition during guest page-fault handling. This sequence can result in a use-after-free, followed by writes after free — a classic pattern used to turn a memory corruption issue into arbitrary code execution.
Public disclosure includes a proof-of-concept exploit that chains the vulnerability and ultimately creates a file named /Zapscape on the host with root ownership. On Intel platforms the scenario requires the L1 guest to have EPT page walk lengths 4 and 5 exposed. No equivalent condition appears in the published information for AMD processors.
No active exploitation in real-world attacks has been observed so far. Nevertheless, the potential scope justifies rapid action, especially in multi-tenant environments. The NVD lists affected versions starting from Linux 5.9, and fixes are already present in the mainline tree and stable branches, including versions 6.6.148, 6.12.101, 6.18.42, 7.1.6 and 7.2 rc5.
The most direct mitigation is to update to a patched stable kernel or install the vendor package containing the backported fix. At the same time, organizations should inventory hosts that offer nested virtualization to untrusted tenants and treat them as patching priorities. If a server does not require nested virtualization, disabling it immediately reduces the attack surface. Administrators should also verify the effective version through their distribution vendor, because some fixes arrive as backports without obvious changes to the upstream version string.
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.