A critical vulnerability (CVE-2024-6387) in OpenSSH allows remote unauthenticated attackers to execute arbitrary code as root on affected machines. This affects Compute Engine VMs running glibc-based Linux distributions with OpenSSH exposed, as well as Google TPU and Container-Optimized OS versions. The vulnerability can be mitigated by applying patches from Linux distributions or Google-provided updated OS images. Runtime mitigation is also available by setting LoginGraceTime to 0 in sshd_config and restarting the sshd service. Additionally, restricting SSH access via firewall rules to trusted networks or disabling SSH until patched reduces exposure.
A speculative execution vulnerability (CVE-2024-28956) affecting Intel Cascade Lake and Ice Lake processors has been identified. Google has applied mitigations across its infrastructure, including Google Cloud, to protect customers. No evidence of exploitation has been reported. Additional mitigations from Intel OEMs and OS partners are forthcoming. Customers do not need to take action at this time. Some performance degradation may occur on long-running 3rd generation or later VMs after OS-level mitigations are applied.
A side channel vulnerability (CVE-2024-45332) affects multiple Intel Xeon processors including CascadeLake, Ice Lake XeonSP, Ice Lake XeonD, Sapphire Rapids, and Emerald Rapids. Google has applied fixes to its infrastructure, including Google Cloud, to protect customers. No evidence of exploitation has been reported. No customer action is required as the mitigation is already in place.
A vulnerability in the Trusted Platform Module (TPM) software affects Shielded VMs using virtual TPM (vTPM). An authenticated local attacker with access to the vTPM interface can send malicious commands exploiting an out-of-bounds memory read, potentially exposing sensitive vTPM data or impacting vTPM availability. Google will proactively update affected systems during standard maintenance windows, and no customer action is required. Limiting vTPM access to administrative users can help reduce risk.
Two new vulnerabilities affecting specific Intel processors have been identified. CVE-2025-21090 allows an unprivileged actor using the AMX and AVX CPU instructions to render the host machine inoperative. CVE-2025-22840 allows an unprivileged actor using the prefetchit CPU instruction to access memory contents without authorization, potentially leading to remote code execution. Google has stated no customer action is required as they will update systems during planned maintenance windows. No evidence of exploitation has been reported.
A vulnerability has been identified in the RDSEED instruction on AMD Zen 5 (Turin) processors. The 16- and 32-bit versions of the RDSEED instruction can silently fail under certain system load conditions, potentially compromising applications that rely on these instructions for cryptographic random number generation. The 64-bit version of RDSEED is not affected and remains safe. AMD is currently investigating this issue. The 64-bit Linux kernel uses the safe 64-bit RDSEED instruction for /dev/[u]random, so those random numbers are not impacted. Applications that synthesize random numbers using the 16- or 32-bit RDSEED instructions should be aware of this insecurity.
A vulnerability in the CPP RCTX instruction on select Arm processors used in Google Cloud Compute Engine Arm VMs (C4A, A4X) allows an attacker with privileged guest kernel access to inhibit TLB invalidations. This can potentially enable unauthorized reading of sensitive data. Google has already applied mitigations to the affected Arm server fleet, and no customer action is required.
A vulnerability identified as CVE-2026-23268, known as CrackArmor, exists in the Linux kernel's AppArmor component on Container-Optimized OS (COS) nodes. This flaw allows unprivileged users to bypass kernel protections, escalate privileges to root, and break local container isolation. The vulnerability is rated high severity. Google recommends upgrading COS nodes to version cos-125-19216-220-57, which contains the fix. For managed services using COS, users should follow the respective upgrade instructions. Fixes for earlier COS milestones 117 and 121 are in progress.
A vulnerability in AMD firmware could allow a malicious hypervisor to alter BIOS settings and Memory Mapped I/O (MMIO) routing configurations, compromising the confidentiality and integrity of Confidential VMs using AMD SEV-SNP guests. Google has implemented mitigations for this issue in Confidential VM instances with AMD SEV-SNP. No customer action is required. The vulnerability is documented as CVE-2025-54510 and is rated medium severity.
A vulnerability in AMD firmware allows a malicious hypervisor to execute arbitrary code on the AMD Secure Processor (ASP), escalating Memory Mapped I/O (MMIO) read and write permissions. This compromises the confidentiality and integrity of SEV-SNP guests. Google has applied mitigations to Confidential VM instances with AMD SEV-SNP, and no customer action is required.
A hardware-level vulnerability has been identified in AMD Zen 2 microarchitecture processors, including EPYC and Ryzen series, involving potential corruption within the micro-operation (OP) cache. Under specific conditions, this flaw (CVE-2025-54518) could allow security boundary bypasses or unauthorized data access. Google has deployed fixes across its infrastructure to mitigate this issue.
CVE-2025-10263 is an architectural vulnerability in certain Arm cores (Neoverse V1, V2, N1) used in Google Cloud Arm-based instances. It allows an attacker at a lower exception level to write to memory owned by a higher exception level, enabling privilege escalation. This flaw does not affect memory reads. Google has secured the infrastructure against VM-to-VM and VM-to-hypervisor attacks, but guest OS-level patches from OS vendors are required to mitigate threats within the guest environment. Mitigations for Container-Optimized OS are in progress.
A vulnerability (CVE-2026-6726, also known as TCGVRT0010) has been identified in the Trusted Computing Group's TPM 2.0 reference implementation code, affecting all published revisions of the code (v1.16, v1.38, v1.59, v1.83, v184). This flaw could allow a privileged local attacker to obtain credentials from a TPM-aware Certificate Authority for a falsified TPM key, enabling the creation of fraudulent TPM 2.0 attestations. Google will proactively update affected systems during standard maintenance windows, and no customer action is required.
An incorrect authorization vulnerability (CVE-2026-85299) was discovered in Google Cloud Compute Engine versions prior to August 31, 2026. This flaw allowed users to exfiltrate disk data without having the required IAM permissions. The vulnerability was patched on August 31, 2026, and no action is required from users.
The PHP2Shell vulnerabilities (CVE-2026-109618 and CVE-2026-109619) affect PHP, which runs on over 70% of websites. These vulnerabilities pose a critical risk, especially for unsupported legacy PHP versions that no longer receive upstream support. Organizations are urged to quickly identify affected PHP deployments and update to fixed versions. Tenable provides solutions to discover vulnerable PHP assets across external attack surfaces, cloud workloads, and web applications, and assists in prioritizing and accelerating remediation efforts.
CVE-2026-115418 is a SQL injection vulnerability in the AWS Cloud Development Kit (CDK) @aws-cdk/aws-redshift-alpha module. This module provides experimental constructs for managing Amazon Redshift users, tables, and privileges. The vulnerability allows crafted user names, comments, or passwords to alter SQL commands executed with Amazon Redshift superuser privileges during deployment, potentially granting access to all cluster users. Exploitation requires the ability to influence the CDK application's construct property values. Versions prior to 2.274.0-alpha.0 are affected.
This report summarizes multiple cyber threats and incidents observed in late October 2026, including large-scale breaches, supply-chain attacks, AI-enabled cybercrime tools, and critical software vulnerabilities. Notable incidents include a cyberattack on Japanese cloud provider Onamae Desktop Cloud affecting over 26,000 servers, a data breach at India's State Bank of India exposing nearly 3,900 customer records, and a supply-chain compromise of the LiteLLM AI gateway. AI-enabled tools are facilitating large-scale fraud and ransomware attacks targeting critical sectors in the United States. Critical PHP vulnerabilities enabling remote code execution are being widely exploited, with most instances unpatched. Oracle and GitLab have released patches for numerous critical vulnerabilities, including a critical remote code execution flaw in GitLab and a privilege escalation vulnerability in Arista VeloCloud Orchestrator that has been exploited in the wild.
Genesys experienced a cyberattack involving unauthorized access to internal business systems, including a learning management system and a customer relationship management environment. The Genesys Cloud, Genesys Engage, and Genesys Engage Cloud platforms were not compromised, and customer and partner data within those platforms remain secure. The attackers accessed and likely downloaded business and account information used to manage customer relationships, including names, phone numbers, business emails, job titles, and company information. Genesys contained the incident by suspending the LMS platform and confirmed full containment by October 23, 2026. The investigation is ongoing, and customers are cautioned to watch for phishing attempts impersonating Genesys.
CVE-2026-89090 is a denial of service vulnerability in the event stream header decoder of AWS SDK for Go v2 versions prior to 2026-03-23. An unauthenticated remote actor can send a crafted event stream response frame with an invalid header value type, causing the application process to panic and terminate. The issue is fixed in version 2026-03-23 and later.
CVE-2026-18061 is an XML External Entity (XXE) vulnerability in the AWS Advanced JDBC Wrapper's optional RemoteQueryCachePlugin. This plugin, when enabled with a shared cache, allows an attacker with write access to insert malicious XML into cached column values. When the application reads these cached results as XML, external entities are resolved, potentially exposing sensitive files accessible to the application process, including database and IAM role credentials. The vulnerability affects versions from 3.3.0 through 4.2.0 and is fixed in version 4.3.0. The plugin is not enabled by default. Mitigation includes disabling the plugin or restricting write access to the shared cache.