Google Cloud has published security bulletin GCP-2026-081 on three Transient Scheduler Attacks (TSA) vulnerabilities in 5th-generation AMD EPYC (Turin) processors, which under certain conditions may allow an attacker to indirectly read data of another process, the operating-system kernel, another virtual machine (VM) or the server itself. The bulletin was published on Tuesday, November 10, 2026 and rates the vulnerabilities’ severity as “Medium”.
For Google Cloud customers the main message is practical: the company has already applied measures that protect against attacks between virtual machines and between a virtual machine and the server hosting it. Protection against attacks inside the same virtual machine, for example between two processes, depends on the customer’s operating system and requires it to be updated.
They are CVE-2024-36350 (TSA-SQ) and CVE-2024-36357 (TSA-L1), and one new one, CVE-2026-0004. The first two had been announced earlier by AMD for previous EPYC processors and now also concern the Zen 5 architecture. The third, like TSA-L1, allows data to be inferred, under conditions, from the level-1 (L1) data cache and information to leak between different privilege levels. TSA-SQ concerns the store queue.
All three belong to the Transient Scheduler Attacks category, side-channel attacks that exploit instruction scheduling during transient execution. As Google Cloud explains, the processor may for a moment use data before confirming that it is valid. If the attacker runs code on the same processor core, they can measure the timing differences that result and infer data from another process, the system kernel, another virtual machine or the server.
Google Cloud says the affected Compute Engine machine series are C4D, N4D, H4D, Z4D and G4, together with the C4D and Z4D bare-metal instances, that is dedicated physical servers without virtualisation. Since Tuesday, November 10 the company is updating the processor information reported by virtual machines, so that updated operating-system kernels enable their own protections. Once the update reaches the virtual machine, the customer must stop and start the virtual machine again, because a simple restart of the operating system is not enough.
Anyone running their own operating system or hypervisor on a bare-metal server must apply their vendor’s fixes when they become available. Anyone running a hypervisor inside a virtual machine (nested virtualisation) follows the procedure for virtual machines. In Google Kubernetes Engine (GKE), updated node images will be provided for the bare-metal servers with Turin processors, while for Cloud Run no action is required.
Google refers to AMD’s security bulletins AMD-SB-7073 and AMD-SB-3055. The first, titled “AMD Transient Scheduler Attacks for Zen 5 Processors”, follows up notice AMD-SN-7029 and explains that Zen 5 processors are affected differently from previous ones. AMD rates CVE-2024-36350 and CVE-2024-36357 at 5.6 on the CVSS 3.1 scale. According to the company, TSA-SQ can lead to data leaking from the kernel to user applications, while TSA-L1 can leak from the host to the guest system, between guest systems, from the kernel to applications and between applications.
For full mitigation, AMD explains, both platform initialisation (PI) firmware updates and operating-system updates are needed. For EPYC 8005 and 9005 series processors, the bulletin gives July 10, 2026 as the date the TurinPI_1.0.0.B package was made available to system manufacturers (OEMs), while for TSA-SQ on EPYC 9005 a SEV firmware update, version 1.3A.05, is also planned. For embedded EPYC 9005 processors the corresponding package, EmbeddedTurinPI_SP5_1005, is dated September 15, 2026. The BIOS update is delivered through each system’s manufacturer.
CVE-2026-0004 is described in bulletin AMD-SB-3055, published on November 10, 2026, which says it was found by the company itself. AMD rates it 5.7 on the CVSS 4.0 scale and provides for EPYC 8005 and 9005 the same firmware, new microcode and operating-system updates for Linux, Windows and VMware.
For prioritising updates, Microsoft’s analysis of 383,000 vulnerabilities is useful, while CISA regularly adds vulnerabilities to its KEV catalogue, as it recently did with the UnrealIRCd and Check Point flaws. Bulletin GCP-2026-081 is on Google Cloud’s security bulletins page.



