AMD has disclosed three vulnerabilities that affect 5th generation AMD EPYC processors (code-named Turin): CVE-2024-36350 and CVE-2024-36357, which AMD previously disclosed for earlier EPYC processors, and a new vulnerability, CVE-2026-0004. Under certain conditions, an attacker could infer data from the store queue or the L1 data cache, potentially leaking sensitive information across privilege boundaries.
Affected Compute Engine machine series: C4D, N4D, H4D, Z4D, and G4, including C4D and Z4D bare metal instances.
Google has applied mitigations that protect against attacks between VMs and between VMs and the host. To protect against attacks inside a VM, such as between processes, you need to update your guest operating system.
VMs: Update your guest operating system when your OS vendor releases fixes. Starting November 10th, Google will update the CPU information that VMs report so that patched guest kernels can turn on their mitigations. After the update reaches your VM, stop and start the VM. Rebooting the guest OS isn't enough.
Bare metal and nested virtualization: If you run your own OS or hypervisor on a bare metal instance, apply your vendor's fixes when they're available. If you run a hypervisor inside a VM, Google will update the CPU information that VMs report so that patched guest kernels can turn on their mitigations. After the update reaches your VM, stop and start the VM. Rebooting the guest OS isn't enough.
GKE: Updated GKE node images for Turin-based bare metal instances will be made available. Upgrading your nodes picks up the CPU information update. This bulletin will be updated once the new node image is available.
Cloud Run: No action is required.
For more information, see AMD security bulletins AMD-SB-7073 and AMD-SB-3055 .
What vulnerabilities are being addressed?
CVE-2024-36350 (TSA-SQ): may allow an attacker to infer data from stores, potentially leaking sensitive information.
CVE-2024-36357 (TSA-L1): may allow an attacker to infer data in the L1 data cache, potentially leaking sensitive information across privilege boundaries.
CVE-2026-0004: may allow an attacker to infer data in the L1 data cache, potentially leaking sensitive information across privilege boundaries.
These are Transient Scheduler Attacks (TSA), a type of side-channel vulnerability. Under certain conditions, the processor can briefly use data before confirming it's valid. An attacker running code on the same processor core may be able to measure the resulting timing differences to infer data from another process, the kernel, another VM, or the host.
Published: 2026-11-09
Security vulnerabilities were discovered in Istio ( ISTIO-SECURITY-2026-009 ).
For instructions and more details, see the Cloud Service Mesh security bulletin .
Published: 2026-11-05
Per advisory VMSA-2026-0008 , Broadcom has identified an out-of-bounds write remote code execution vulnerability in the SDDC Manager Node.js Brotli decoder. This impacts only VMware solution on Google Cloud running VMware Cloud Foundation 9.1.x and does not impact Google Cloud VMware Engine.
To remediate, apply the Broadcom-recommended workarounds outlined in the VMSA-2026-0008 advisory.
For more information, see the VMware solution on Google Cloud security bulletin .
Published: 2026-11-04
A vulnerability (CVE-2026-98432) was discovered in the Linux kernel IPv4 TCP stack. The flaw can cause a kernel panic or a container escape (root code execution on the node). An unprivileged process in a container can trigger it locally, without special capabilities such as CAP_NET_RAW . A network attacker can also trigger it by sending TCP packets with IPv4 options to a listener on the node or on the cluster control plane.
The network attack requires access to a TCP listener on your nodes, Pods, or the control plane's IP-based endpoint. Clusters that restrict this access to trusted sources, for example with firewall rules and control plane authorized networks, are not exposed to network attacks.
GKE Standard clusters and GKE Autopilot clusters are impacted.
For instructions and more details, see the GKE security bulletin .
Published: 2026-11-03
Following the private-key compromise of intermediate Certificate Authorities (CAs) associated with eMudhra (emSign), outbound TLS connections trusting affected roots—specifically emSign ECC Root CA - G3 —are vulnerable to Man-in-the-Middle (MITM) interception. An attacker possessing compromised intermediate keys can issue fraudulent TLS certificates for arbitrary domain names. Outbound HTTPS connections made from Apigee runtimes (such as TargetEndpoints, TargetServers, ServiceCallouts, and outbound JWKS policy lookups) using default or unmanaged system trust stores may accept forged certificates. This security bulletin outlines required remediation steps for Apigee, Apigee Hybrid, Apigee Edge (SaaS), and Apigee Edge for Private Cloud (OPDK).
For more information, see the Apigee security bulletin .
Published: 2026-11-02
A security vulnerability was discovered in Istio ( ISTIO-SECURITY-2026-008 ).
For instructions and more details, see the Cloud Service Mesh security bulletin .
Published: 2026-11-02
On Saturday, October 17, 2026, Google received a report from a security researcher regarding the compromise of private keys associated with eight eMudhra subordinate Certification Authority (CA) certificates, including those cross-signed by AAA Certificate Services. Consequently, these CA certificates are no longer trusted and are being revoked.
Google Cloud infrastructure has not been breached. Security telemetry shows no evidence of exploitation against Google Cloud workloads.
Applications built with the Google Cloud SDK Libraries are affected if their TLS trust store still accepts emSign ECC Root CA - G3 , emSign Root TLS CA - G3 , or AAA Certificate Services . The Google Cloud SDK Libraries themselves don't bundle CA certificates, with one exception: Java's com.google.api-client: google-api-client before 2.9.2. In all other cases, the trust store comes from a transport dependency (including the Google-maintained gRPC packages), the language runtime, or the operating system, so the fix is an update to those rather than to the Google Cloud SDK Libraries. In Java, Ruby, and PHP, upgrading the Google client libraries also pulls the fix in.
The sections below give the action for each language.
Find your language below and apply the recommended actions. Then rebuild and redeploy your container images.
The following packages are affected:
certifi earlier than 2026.10.19 (REST transports).
httplib2 earlier than 0.32.1, used by google-api-python-client and google-auth-httplib2 ; its bundled trust store is used when certifi is not installed.
grpcio earlier than 1.84.1 (gRPC transports); bundled root store, does not read the operating system trust store.
You can take the following actions to resolve these issues:
Upgrade certifi to 2026.10.19 or later.
Upgrade httplib2 to 0.32.1 or later.
Upgrade grpcio to 1.84.1 or later. Patch releases for earlier release lines are being published; see GHSA-2xm2-c8xx-p9vh for the current list of fixed versions.
Advisories: GHSA-6q48-6c7w-9gw2 ( certifi ), GHSA-2xm2-c8xx-p9vh ( grpcio ).
The following packages and trust stores are affected:
com.google.api-client: google-api-client earlier than 2.9.2, when the HTTP transport is created with GoogleNetHttpTransport. newTrustedTransport() . Versions earlier than 2.9.0 always use a bundled trust store that includes AAA Certificate Services ; versions 2.9.0 and 2.9.1 use it when the Java Development Kit (JDK) trust store cannot be loaded.
Google API service library packages ( com.google.apis: google-api-services-* ) with a version suffix earlier than -2.9.2 , which depend on an affected google-api-client .
The JDK trust store ( cacerts ), used by all other Google client transports, and the Windows certificate store on Windows.
You can take the following actions to resolve these issues:
Upgrade google-api-client to 2.9.2 or later, or com.google.cloud: libraries-bom to 26.91.0 or later.
If your build declares a service library without google-api-client , upgrade the service library to a release whose version ends in -2.9.2 or later (for example, google-api-services-bigquery: v2-rev20260922-2.9.2 ), or declare com.google.api-client: google-api-client:2.9.2 directly.
If you use Spring Framework on Google Cloud, upgrade to the current patch release of your line: 8.3.1 , 7.5.2 , 6.5.12 , 3.9.19 , or later; these import libraries-bom 26.91.0.
Apply your JDK vendor's security update.
On Windows, apply the Windows root certificate update.
Advisory: GHSA-m4gc-hcgx-wmc7 ( google-api-client ).
The following packages and trust stores are affected:
grpc gem earlier than 1.84.1 (gRPC transports). The package loads its bundled trust store, and does not read the operating system trust store.
The operating system's OpenSSL trust store (REST transports).
You can take the following actions to resolve these issues:
Run bundle update grpc to 1.84.1 or later.
Alternatively, run bundle update for your google-cloud-* gems; current releases require grpc 1.84.1 or later and pull it in.
Update the operating system trust store.
Advisory: GHSA-p3vr-xp4c-r8fh ( grpc ).
The following packages and trust stores are affected:
Composer package grpc/grpc earlier than 1.84.1 (gRPC transports). The package loads its bundled trust store and does not read the operating system trust store.
The operating system's trust store (REST transports).
You can take the following actions to resolve these issues:
Run composer update grpc/grpc to 1.84.1 or later.
Alternatively, run composer update google/gax to 1.51.2 or later; it requires grpc/grpc 1.84.1 or later and pulls it in.
Update the operating system trust store.
Advisory: GHSA-gvrc-7wf9-p7hg ( grpc/grpc ).
The following packages and trust stores are affected:
The Node.js runtime's built-in root certificate store.
The deprecated native grpc npm package, which bundles a root store and will not be updated.
You can take the following actions to resolve these issues:
Upgrade Node.js to 26.12.1, 24.22.1, or 22.23.4 or later.
If your application still uses the deprecated grpc npm package, migrate to @grpc/grpc-js .
The following trust stores and toolchains are affected:
The host or container image trust store.
Go toolchains earlier than 1.26.10 / 1.27.3 ( GO-2026-6809/ CVE-2026-111943 ). Later toolchains additionally reject the compromised intermediate certificates in crypto/x509 regardless of the trust store.
You can take the following actions to resolve these issues:
Rebuild and redeploy Go binaries and container images with Go 1.26.10, 1.27.3, or later.
Use an updated base image when rebuilding container images.
The following packages and trust stores are affected:
The operating system trust store used by Grpc.Net.Client and HttpClient . On Windows this includes emSign Root TLS CA - G3 as a direct root until the Windows update is applied.
The legacy Grpc.Core package, which bundles a root store and is not maintained.
You can take the following actions to resolve these issues:
Apply operating system updates.
If your application references the legacy Grpc.Core package, migrate to Grpc.Net.Client .
The following trust stores and code are affected:
The operating system or container image trust store, used by REST transports (libcurl) and by gRPC where a system root store is found.
gRPC versions earlier than 1.84.1, where a bundled roots.pem with affected certificates is used as the fallback when no system root store is available.
You can take the following actions to resolve these issues:
Update the operating system or container base image trust store.
Rebuild against gRPC 1.84.1 or later if gRPC's fallback roots.pem is used.
The following packages and trust stores are affected:
rustls-webpki earlier than 0.103.16 ( RUSTSEC-2026-0382 ).
webpki-root-certs earlier than 1.0.10 ( RUSTSEC-2026-0383 ), or webpki-roots earlier than 1.0.10 ( RUSTSEC-2026-0381 ), whichever root store crate your build uses.
The operating system trust store, for builds that use it instead of a root store crate.
You can take the following actions to resolve these issues:
Run cargo update , then rebuild and redeploy.
Apply operating system updates if your build uses the system trust store.
The following packages and trust stores are affected:
The operating system or container image trust store used by AsyncHTTPClient and grpc-swift-2 ( Security.framework on macOS; the system CA bundle on Linux). AsyncHTTPClient , grpc-swift-2 , and the Google Cloud SDK Libraries do not bundle certificates and are not affected.
AsyncHTTPClient , grpc-swift-2 , and the Google Cloud SDK Libraries do not bundle certificates and are not affected.
gRPC Objective-C CocoaPod ( GHSA-mm89-g5jq-mmfq ) does not apply to Google Cloud SDK Libraries.
You can take the following actions to resolve these issues:
Apply operating system updates.
To confirm an environment is remediated, verify that none of the following certificates is present in the trust store your application uses:
emSign ECC Root CA - G3 — SHA-256 86:A1:EC:BA: 08:9C:4A:8D: 3B:BE:27:34: C6:12:BA:34: 1D:81:3E:04: 3C:F9:E8:A8: 62:CD:5C:57: A3:6B:BE:6B
emSign Root TLS CA - G3 — SHA-256 7D:D7:8D:5F: 4F:13:45:9A: 83:DF:F9:AB: BB:A6:2E:DB: AF:6F:2D:10: 2B:F2:57:FD: 71:2F:4D:9F: 27:46:ED:8D (issuer of six of the eight compromised TLS intermediates; cross-signed by emSign ECC Root CA - G3 and trusted directly as a root in the Windows certificate store)
AAA Certificate Services — SHA-256 D7:A7:A0:FB: 5D:7E:27:31: D7:71:E9:48: 4E:BC:DE:F7: 1D:5F:0C:3E: 0A:29:48:78: 2B:C8:3E:E0: EA:69:9E:F4
If you have questions or need assistance, Cloud Customer Care and reference issue #576444463 .
What vulnerabilities are being addressed?
The private keys for eight eMudhra (emSign) subordinate CA certificates were generated with insufficient cryptographic randomness and can be recovered from the public certificates. A remote attacker with a network position between a client and a server can forge TLS certificates for any domain, including Google API endpoints, and intercept or modify traffic from clients that still trust the issuing roots. Because most non-browser TLS clients do not check certificate revocation, removing the root certificates from the client's trust store is the effective mitigation.
The Google Cloud platform bulletin for this incident GCP-2026-071 covers Google Cloud services, base images, and the Google Cloud CLI. This bulletin covers applications built with the Google Cloud SDK Libraries.
Additional vulnerability references:
GHSA-6q48-6c7w-9gw2 ( certifi )
GHSA-2xm2-c8xx-p9vh ( grpcio )
GHSA-p3vr-xp4c-r8fh ( grpc RubyGems)
GHSA-gvrc-7wf9-p7hg ( grpc/grpc Composer)
GHSA-mm89-g5jq-mmfq ( gRPC Objective-C CocoaPod)
GHSA-m4gc-hcgx-wmc7 ( google-api-client Java)
GO-2026-6809/ CVE-2026-111943
Published: 2026-10-28
A Deserialization of Untrusted Data vulnerability was discovered in the SubWorkflow task in Application Integration versions prior to September 11, 2026.
No customer action is required. This vulnerability was patched on September 11, 2026.
What vulnerabilities are being addressed?
An authenticated user could use a maliciously crafted serialized object to execute arbitrary code.
Published: 2026-10-26
An incorrect authorization vulnerability was discovered in Compute Engine prior to August 31, 2026.
No action is required from you. This vulnerability was patched on August 31, 2026.
What vulnerabilities are being addressed?
An incorrect authorization vulnerability in Compute Engine versions prior to August 31, 2026 allows a user to exfiltrate disk data without the required IAM permissions.
Published: 2026-10-24
Two vulnerabilities in PHP core, CVE-2026-109618 and CVE-2026-109619 ("PHP2Shell"), allow an unauthenticated attacker to execute code remotely on a server running a vulnerable PHP version. They are fixed in PHP 8.2.35, 8.3.36, 8.4.27, and 8.5.12. No fixed release exists for PHP 8.1 or earlier.
The impact on Apigee is limited to Drupal-based Apigee developer portals, which customers deploy and operate. Other Apigee products don't use PHP and aren't affected.
For instructions and more details, see the Apigee security bulletin .
Published: 2026-10-23
2026-11-02 Update: Added Google Cloud SDK Libraries to the list of affected products.
2026-10-28 Update: Added Managed Service for Apache Spark and Cloud Profiler to the list of affected products.
We will continue to update the list of affected products with links to product-specific guidance as it becomes available.
On Saturday, October 17, 2026, Google received a report from a security researcher regarding the compromise of private keys associated with eight eMudhra subordinate Certification Authority (CA) certificates, including those cross-signed by AAA Certificate Services. Consequently, these CA certificates are no longer trusted and are being revoked.
Although Google Cloud infrastructure remains uncompromised, the following Google Cloud and Firebase products, base images, and client SDKs are impacted:
Container-Optimized OS
Google Kubernetes Engine
Cloud Functions for Firebase
AlloyDB for PostgreSQL
Firebase App Distribution
Google Distributed Cloud
Managed Service for Apache Spark
Google Cloud SDK Libraries
Google Cloud is actively managing this issue across our infrastructure and platform services, and Google Cloud infrastructure has not been breached. Security telemetry shows no evidence of exploitation against Google Cloud workloads, and proactive mitigations are in place across Google-managed environments to block and distrust the affected certificate authority certificates.
For environments and dependencies that you manage directly, take the following actions:
Red Hat Enterprise Linux (RHEL): Follow RHSB-2026-012 .
Debian: Update to the latest ca-certificates package ( Bug 1151446 ).
Windows: Install the latest Windows updates.
Container-Optimized OS (COS): Upgrade or restart nodes to pick up current COS milestone releases, or apply the cos_ca_cert_mitigation tool.
Google Cloud CLI: Update to the latest gcloud CLI release to ensure bundled dependencies include updated certificate stores.
Service-Specific Guidance: For managed Google Cloud and Firebase services, such as GKE, Serverless runtimes, Managed Databases, Firestore, Firebase App Distribution, and Confidential Space, Google Cloud is rolling out updates across managed fleets, and service-specific details, release notes, and customer communications will be published through the respective product documentation and official support channels as they become available. Please review individual service documentation for instructions tailored to your deployments.
If you have any questions or require assistance, please Cloud Customer Care and reference issue #576444463.
What vulnerabilities are being addressed?
The private keys for eight eMudhra (emSign) subordinate Certification Authority (CA) certificates were generated using insufficient cryptographic randomness (weak entropy).
This weakness allows a remote attacker with network access to reconstruct private keys, forge trusted TLS certificates, and perform Man-in-the-Middle (MitM) interception against TLS clients, containers, or SDKs that have not yet removed trust in these subordinate CAs.
Red Hat ( RHSB-2026-012 )
Ubuntu ( USN-8944-1 )
Debian (DSA-6572-1 / Bug 1151446 )
Published: 2026-10-21
2026-10-28 Update: For Cloud Run , Cloud Run functions , and Google App Engine Standard , all supported versions of PHP 8.2 and later are patched. Take immediate protective action by redeploying your resources with updated dependencies.
Two remote code execution vulnerabilities were found in the open-source PHP language . While Google Cloud itself is not vulnerable, users of this language running on Google Cloud may be vulnerable.
The following language versions are affected by this vulnerability:
All PHP versions between 5.4 and 8.5
The following framework versions include fixes for this vulnerability:
PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35
Customers should take immediate action to protect their workloads by redeploying their workloads with updated dependencies. Some workloads may be automatically patched and updated to the latest PHP if they are on Google App Engine Standard or one of Cloud Run, Cloud Run functions with automatic updates enabled. See the blog post for more information.
Customers using Artifact Analysis receive notifications of these vulnerabilities on both new and existing artifacts to help them identify at-risk workloads.
Published: 2026-10-19
Security vulnerabilities were discovered in Istio and Envoy Proxy ( ISTIO-SECURITY-2026-007 ).
For instructions and more details, see the Cloud Service Mesh security bulletin .
Published: 2026-10-14
An Incorrect Authorization vulnerability in the AuthConfig validation and integration execution runtime in Application Integration versions prior to August 27, 2026.
No customer action to resolve this vulnerability is required. This vulnerability was patched on August 27, 2026.
Application Integration helps to enhance security against authorization vulnerabilities by requiring the iam.serviceAccounts.actAs permission on the run-as service account to publish or test an integration. Integrations created on or after October 15, 2026, must have a run-as service account to publish or test scheduled or event triggers. Starting January 15, 2027 (UTC), this requirement also applies to existing integrations created before October 15, 2026. For more information, see Prepare for upcoming authorization changes .
What vulnerabilities are being addressed?
An authenticated user could escalate privileges and impersonate a service account in the Google Cloud project.
Published: 2026-10-12
A Denial-of-Service (DoS) vulnerability was discovered in Envoy Proxy when an HTTP filter (such as ext_proc with route_cache_action: RETAIN ) mutates the :path header after route selection on a route configured with prefix_rewrite .
For instructions and more details, see the Cloud Service Mesh security bulletin .
Published: 2026-09-28
A Confused Deputy vulnerability was discovered in the Email Task component in Application Integration versions prior to June 30, 2026.
No customer action is required. This vulnerability was patched on June 30, 2026.
What vulnerabilities are being addressed?
An authenticated attacker could read and exfiltrate arbitrary Google-internal files using a crafted attachment path.
Published: 2026-09-28
A Deserialization of Untrusted Data vulnerability was discovered in the JavaScript Task in Application Integration versions prior to June 28, 2026.
No customer action is required. This vulnerability was patched on June 28, 2026.
What vulnerabilities are being addressed?
An authenticated user with standard permissions could use a specially crafted script to run arbitrary code on the shared production servers.
Published: 2026-09-28
An Incorrect Authorization vulnerability was discovered in the task configuration in Application Integration versions prior to June 17, 2026.
No customer action is required. This vulnerability was patched on June 17, 2026.
What vulnerabilities are being addressed?
An authenticated user could use an internal-only task type to execute arbitrary internal RPCs from the Google-internal production network under a privileged identity.
Published: 2026-09-16
An Improper Privilege Management vulnerability in Google Security Operations SOAR was patched with version 6.3.85, and no customer action is needed. The vulnerability allowed an authenticated attacker to escalate privileges to system-level administrative access using a crafted internal authentication header.
No customer action is required. All customers have been automatically upgraded to the fixed version: 6.3.85 or higher.
Published: 2026-09-11
Multiple security vulnerabilities were discovered in Slurm that affect Cluster Toolkit blueprints that reference specific image versions. These vulnerabilities affect the slurmstepd daemon, RPC request handling, and the accounting database.
For instructions and more details, see the Cluster Toolkit security bulletin .
Published: 2026-09-09
A security vulnerability ( GHSA-p7v4-vr35-mj6f , CVE assignment pending) in containerd's CRI implementation allows a container restored from an untrusted checkpoint through the CreateContainer API to bypass the destination security context and execute with elevated privileges.
GKE clusters are not vulnerable by default. GKE node images do not include the criu tool.
No immediate customer action is required for default clusters. If you install custom runtime software or node tools on your nodes that include the criu binary, refer to the security bulletin for recommended actions.
What vulnerabilities are being addressed?
For more information, see the GKE security bulletin .
Published: 2026-09-04
2026-09-08 Update: Added link to the Cluster Toolkit security bulletin.
A security flaw in the Slurm sbcast tool (CVE-2026-65107) lets shared library files bypass security checks and can crash nodes in your cluster.
For instructions and more details, see the following bulletins:
Cluster Toolkit security bulletin
Cluster Director security bulletin
Published: 2026-09-04
A Missing Authorization vulnerability was discovered in the HTTP Connector in Integration Connectors versions prior to December 11, 2025.
No customer action is required. This vulnerability was patched on December 11, 2025.
What vulnerabilities are being addressed?
An authenticated attacker could use an unauthorized service account attachment to escalate privileges and take over a Google Cloud project.
Published: 2026-09-02
A missing project permission check in GKE Multi-Cloud (CreateAttachedCluster, CreateAwsCluster, CreateAzureCluster) APIs allowed an attacker to register an attached cluster into an arbitrary target project's Workload Identity Federation for GKE. This registration allowed unauthorized creation of Workload Identity tokens and impersonation of Kubernetes Service Accounts that have bindings in the target project through the Workload Identity Federation for GKE configuration.
For instructions and more details, see the GKE security bulletin
Published: 2026-08-26
A series of vulnerabilities were discovered in Envoy Proxy.
For instructions and more details, see the Cloud Service Mesh security bulletin .
Published: 2026-08-26
An Improper Input Validation vulnerability was discovered in the JDBC driver in BigQuery Data Transfer Service versions prior to May 1, 2026.
No customer action is required. This vulnerability was patched on May 1, 2026.
What vulnerabilities are being addressed?
An authenticated attacker could use crafted JDBC connection string parameters to achieve remote code execution in the connector container and escalate privileges in the tenant project.
Published: 2026-08-25
A critical unauthenticated Remote Code Execution (RCE) vulnerability exists in .js and libheif when processing malicious image files. Google Cloud infrastructure is not directly vulnerable, but customer workloads running .js on Google Cloud (e.g., Cloud Run, GKE, App Engine) may be affected.
Google Cloud backend services are not directly impacted, and no action is required to secure the underlying Google Cloud infrastructure. However, customers hosting .js applications on Google Cloud must take immediate action to secure their own workloads. We recommend that you manually upgrade your .js deployments to one of the following versions (or later) in your package.json : 16.3.3 15.5.24 Customers utilizing libheif should monitor for upstream OS patches and rebuild their container base images accordingly. Redeploy your updated workloads to ensure running containers utilize the patched versions.
What vulnerabilities are being addressed?
The vulnerabilities, GHSA-2xp9-vwfh-vxw4 and GHSA-g89c-p67h-r497 , allow an attacker to execute arbitrary code within the context of the application by supplying a crafted image file during .js image optimization. This issue occurs due to how the underlying libheif library processes clean aperture boxes in HEIF/AVIF images.
Published: 2026-08-11
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).
No customer action is required. Google will proactively update your systems during your standard and planned maintenance windows.
What vulnerabilities are being addressed?
For more information, see the Compute Engine security bulletin .
Published: 2026-08-11
Google is aware of several security vulnerabilities affecting Intel® Trust Domain Extensions (TDX) firmware that can compromise confidential guest integrity. These vulnerabilities could allow a privileged host adversary to bypass attestation checks, access restricted registers, or decrypt normally protected guest memory.
What Google products are affected?
All Confidential VM instances relying on Intel TDX technology.
Google has proactively applied these firmware upgrades to our server fleet to mitigate these vulnerabilities. No action is required for customers that did not receive a separate direct advisory to upgrade.
For more information, see Intel's PSIRT technical advisories: INTEL-TA-01404 , INTEL-TA-01428 , INTEL-TA-01419 , INTEL-TA-01439 , INTEL-TA-01442 , INTEL-TA-01436 .
Published: 2026-08-07
A security vulnerability has been identified in the Kernel-based Virtual Machine (KVM) x86 shadow Memory Management Unit (MMU) impacting both Intel and AMD platforms.
No action is required for managed Compute Engine virtual machines. Because the vulnerability resides in the host hypervisor, Google has mitigated all affected Intel and AMD-based host infrastructure transparently via live patching without requiring customer VM downtime, reboots, or manual upgrades.
If you operate self-managed virtualized environments or custom host hypervisors outside standard managed Compute Engine infrastructure, you should ensure your host Linux kernel is updated with the upstream patch as soon as it is made available by your operating system distribution vendor.
What vulnerabilities are being addressed?
This is a KVM vulnerability that could lead to a VM escape. There has been no active exploitation observed, and this is a proactive patching effort.
Published: 2026-07-31
2026-08-04 Update: The VMware patch release version is 1.33.1200, not 1.33.1100 as stated in the initial bulletin.
The following vulnerabilities have been discovered in containerd (the GDC container runtime). These vulnerabilities allow attackers with permissions to create Pods to bypass Kubernetes security boundaries and perform host compromise, cache poisoning, and denial of service. While these vulnerabilities are critical in the context of containerd, the requirement to have cluster privileges to create Pods to exploit them means they are considered High according to GDC (software only) vulnerability classification. CVE-2026-50195 (Critical) : containerd's CRI checkpoint import process fails to validate image references. An attacker with permissions to create Pods can use a crafted checkpoint image to poison the node's local image cache, causing other pods to use a malicious image. CVE-2026-53488 (Critical) : CRI plugin propagates labels from an image config to a container without validation. This may result in executing an arbitrary command on the host. CVE-2026-53492 (Critical) : CRI implementation improperly trusts Container Device Interface (CDI) annotations during container restoration. This allows an attacker to inject arbitrary CDI configurations (such as host mounts and device nodes) into restored containers, bypassing resource allocation and device plugin enforcement. CVE-2026-53489 (High) : CRI plugin restores container.log without validating a symlinked path, allowing an attacker to read arbitrary host files via kubectl logs. CVE-2026-47262 (Moderate) : A vulnerability in containerd allows a maliciously crafted image to cause memory exhaustion (DoS) of the containerd process. These vulnerabilities affect all GDC (software only) configurations using Ubuntu node images.
CVE-2026-50195 (Critical) : containerd's CRI checkpoint import process fails to validate image references. An attacker with permissions to create Pods can use a crafted checkpoint image to poison the node's local image cache, causing other pods to use a malicious image.
CVE-2026-53488 (Critical) : CRI plugin propagates labels from an image config to a container without validation. This may result in executing an arbitrary command on the host.
CVE-2026-53492 (Critical) : CRI implementation improperly trusts Container Device Interface (CDI) annotations during container restoration. This allows an attacker to inject arbitrary CDI configurations (such as host mounts and device nodes) into restored containers, bypassing resource allocation and device plugin enforcement.
CVE-2026-53489 (High) : CRI plugin restores container.log without validating a symlinked path, allowing an attacker to read arbitrary host files via kubectl logs.
CVE-2026-47262 (Moderate) : A vulnerability in containerd allows a maliciously crafted image to cause memory exhaustion (DoS) of the containerd process.
For GDC software only on bare metal, the following patches will contain fixes for the vulnerabilities issue:
For GDC software only on VMware, the following patches will contain fixes for the vulnerabilities:
Published: 2026-07-29
Per advisory VMSA-2026-0006, multiple vulnerabilities in VMware ESXi, and vCenter were privately reported to Broadcom. We are in the process of applying the necessary patches supplied by Broadcom. There are no known workarounds for these reported vulnerabilities.
Once patched, your VMware Engine deployments should be running vCenter and ESXi 8.0 U3k.
Google recommends customers to monitor their workloads on VMware Engine for any unusual activities.
Published: 2026-07-22
A reflected Cross-Site Scripting (XSS) vulnerability was discovered in Google Cloud Looker. An attacker could craft a malicious URL that, when opened by an authenticated administrator, would allow the attacker to execute arbitrary scripts on their behalf and potentially compromise the administrator account.
For Looker-hosted instances, no action is required.
For self-hosted Looker instances, update your Looker instances as soon as possible. This vulnerability has been patched in all supported versions of Looker for self-hosted instances. The following versions have all been updated to fix this vulnerability:
Looker 26.8.7 and all later versions
What vulnerabilities are being addressed?
For more information, see CVE-2026-15810 .
Published: 2026-07-13
A privilege escalation vulnerability was addressed in Developer Connect. Previously, for GitLab Enterprise and Bitbucket Data Center connections, when Secret Manager secrets were retrieved, permissions were checked against the Developer Connect service agent (P4SA) credentials only. Developer Connect now validates that both the calling principal and the P4SA have the required permissions on the referenced secrets.
For instructions and more details, see the Developer Connect security bulletin .
Published: 2026-07-13
A Missing Authorization vulnerability was discovered in repositories in BigQuery, Dataform, and Colab Enterprise.
No customer action is required. Google has already applied mitigations to all impacted products and services.
What vulnerabilities are being addressed?
During repository creation, an authenticated attacker could potentially escalate their permissions and perform cross-tenant repository takeover.
Published: 2026-07-06
A virtualization vulnerability has been identified in the KVM x86 shadow paging and nested virtualization configurations. Because an attacker operating a virtual machine with nested virtualization could escape hypervisor boundary isolation to compromise the underlying physical host, any x86 virtual machine (whether nested or non-nested) hosted on an Intel-based server supporting nested virtualization is potentially exposed.
Google is deploying live hypervisor hotpatches across all managed Compute Engine host servers globally. No action is required for managed Compute Engine virtual machines or Google Kubernetes Engine clusters. Because remediation is performed transparently at the physical host hypervisor level, customer VM downtime, reboots, or manual upgrades are not required.
Customers operating self-managed virtualized environments or custom host hypervisors outside standard managed Compute Engine infrastructure should ensure their host Linux kernel is updated with the upstream patch as soon as it is made available by their operating system vendor.
What vulnerabilities are being addressed?
The vulnerability (CVE-2026-53359) exploits a use-after-free error in the x86 shadow paging and nested page table translation routines. Google has observed no evidence of active customer exploitation in production environments. Live patching and host-level monitoring have been implemented globally to mitigate risk and detect exploit attempts.
Published: 2026-06-29
A vulnerability was detected in Envoy Proxy where blocked QPACK decoding can cause a Denial-of-Service Attack against the HTTP/3 stack.
For instructions and more details, see the Cloud Service Mesh security bulletin .
Published: 2026-06-25
A vulnerability was detected in Application Integration's JavaScript task, which was using the Rhino JavaScript engine. This only impacted tasks published before January 2025.
For details and instructions, see the Application Integration security bulletin .
Published: 2026-06-24
A vulnerability was found in Firebase Studio where the GetSignedGcsUrl RPC allowed authenticated users to list buckets and download deployment source code of other tenants.
No action is required to mitigate this vulnerability as the fix has been deployed to the backend service.
As a precautionary measure, users who stored sensitive information, such as API keys (for example, GEMINI_API_KEY ), within their Firebase Studio workspace may choose to rotate these keys. For instructions, see the Firebase Studio troubleshooting guide .
Published: 2026-06-24
A privilege escalation vulnerability was addressed in Cloud Build. Previously, for GitLab Enterprise and Bitbucket Data Center connections, when Secret Manager secrets were retrieved, permissions were checked against the Cloud Build service agent (P4SA) credentials only. Cloud Build now validates that both the calling principal and the P4SA have the required permissions on the referenced secrets.
For instructions and more details, see the Cloud Build security bulletin .
Published: 2026-06-24
A recent security investigation was conducted regarding log4j vulnerabilities (CVE-2026-34480 and CVE-2026-34477) reported in Apigee Edge for Private Cloud. Google has determined that Apigee Edge for Private Cloud is not vulnerable to these CVEs. No customer action is required.
For more information, see the Apigee security bulletin .
Published: 2026-06-23
A series of vulnerabilities were discovered in Envoy Proxy.
For instructions and more details, see the Cloud Service Mesh security bulletin .
Published: 2026-06-22
A vulnerability in Cloud Logging could have allowed attackers to hijack log sink destinations by recreating the target Cloud Storage bucket in a project controlled by the attacker. This issue could have resulted in the continuous routing of sensitive logs to an unauthorized third party.
For more information, see the Google Cloud Observability security bulletin .
Published: 2026-06-22
A vulnerability was found in App Engine where the GetDashboardAppStats GraphQL private API operation in the Google Cloud console leaked cross-tenant request logs.
No action is required. This vulnerability has been fixed.
Published: 2026-06-18
2026-06-20 Update: Added GKE patch versions containing the fixes for Container-Optimized OS node images for minor versions 1.35 and 1.36. Patches for Ubuntu node images are still pending and in progress.
2026-06-19 Update: Added GKE patch versions containing the fixes for Container-Optimized OS node images for minor versions from 1.30 to 1.34. Patches for Ubuntu node images and for minor version 1.35 and 1.36 for Container-Optimized OS node images are in progress.
Multiple vulnerabilities have been discovered in containerd (the GKE container runtime). These vulnerabilities allow attackers with permissions to create pods to bypass Kubernetes security boundaries and perform host compromise, cache poisoning, and denial of service.
For instructions and more details, see the GKE security bulletin
Published: 2026-06-09
ARM has announced CVE-2025-10263, an architectural issue affecting some Arm cores which lets an attacker bypass translation stages or GPT protections under certain conditions. This vulnerability lets an attacker at a lower exception level to write to memory owned by a higher exception level, thereby escalating privileges. This issue does not affect memory reads.
For more information, see the following bulletins:
Compute Engine security bulletin
Published: 2026-06-08
A vulnerability was found in Envoy where HTTP/2 downstream request processing allow an unauthenticated remote client to trigger excessive memory consumption, potentially resulting in OOM termination of the Envoy process and denial of service.
For instructions and more details, see the Cloud Service Mesh security bulletin .
Published: 2026-05-20
A vulnerability was found in Apigee where the IntegrationRegion parameter in the SetIntegrationRequest policy lacks validation, allowing for Server-Side Request Forgery (SSRF) and service account token exfiltration. The issue arises when an attacker can control a flow variable used for IntegrationRegion , leading to requests being sent to an attacker-controlled host with the service account token.
Published: 2026-05-14
2026-07-16 Update: The following versions of GKE are updated with code to fix this vulnerability on Ubuntu. Upgrade your Ubuntu node pools to the following versions or later:
A container breakout vulnerability CVE-2026-46300 has been found in the Linux kernel, known as Fragnesia. It allows an unprivileged local attacker to escalate to root on the host.
For instructions and more details, see the following bulletins:
GKE security bulletin
GDC software for VMware security bulletin
GKE on AWS security bulletin
GKE on Azure security bulletin
GDC software for bare metal security bulletin
Published: 2026-05-12
AMD has identified a hardware-level vulnerability in Zen 2 microarchitecture processors (including EPYC and Ryzen series) involving potential corruption within the micro-operation (OP) cache. Under specific conditions, this issue (AMD-SN-7052 / CVE-2025-54518) could lead to security boundary bypasses or unauthorized data access. We have deployed fixes across Google infrastructure to mitigate these issues.
For more information, see the Compute Engine security bulletin .
Published: 2026-05-12
Researchers discovered a vulnerability in AMD firmware that, due to missing protection, could allow a malicious hypervisor to execute arbitrary code on the AMD Secure Processor (ASP). This allows for the escalation of Memory Mapped I/O (MMIO) read and write permissions, which compromises the confidentiality and integrity of SEV-SNP guests.
For more information, see the Compute Engine security bulletin .
Published: 2026-05-11
2026-06-24 Update: Added patch versions for GKE.
2026-05-20 Update: Added CVE-2026-43500 and added CVE IDs to exploit paths.
The following vulnerabilities were discovered in the Linux kernel that can lead to a privilege escalation on Container-Optimized OS and Ubuntu nodes: CVE-2026-43284 CVE-2026-43500
For instructions and more details, see the following bulletins:
GKE security bulletin
GDC software for VMware security bulletin
GKE on AWS security bulletin
GKE on Azure security bulletin
GDC software for bare metal security bulletin
Published: 2026-05-07
Microsoft is updating the Secure Boot certificates originally issued in 2011 to ensure Windows devices continue to verify trusted boot software. These older certificates begin expiring in June 2026. Devices that haven't received the newer 2023 certificates will continue to start and operate normally, and standard Windows updates will continue to install. However, these devices will no longer be able to receive new security protections for the early boot process, including updates to Windows Boot Manager, Secure Boot databases, revocation lists, or mitigations for newly discovered boot-level vulnerabilities. Also, Secure Boot certificate expirations starting in June 2026 affect Linux systems that use Secure Boot.
Google recommends that customers update their Windows VMs by taking appropriate actions as recommended by Microsoft. Distributions like Ubuntu, Red Hat, and Fedora are already working to provide updated packages signed with the new 2023 key. Refer also to the Broadcom documentation to resolve errors and warnings in VMware virtual machines as Secure Boot certificates approach expiration. After June 2026, systems lacking the 2023 certificate updates may experience failures during new operating system installations or while updating the existing bootloader firmware.
Published: 2026-05-05
CVE-2026-31431 , also known as "Copy Fail," is a high-severity local privilege escalation (LPE) vulnerability in the Linux kernel that allows an unprivileged user to gain root access. Disclosed in late April 2026, it stems from a logic flaw in the kernel's cryptographic subsystem (algif_aead) introduced in 2017.
Google recommends that customers protect their Linux Guest VMs by updating the kernel on all Linux VMs. Major distributions have released or are rolling out fixes.
Published: 2026-05-01
The following vulnerabilities were discovered in the Linux kernel that can lead to a privilege escalation on Container-Optimized OS nodes: CVE-2026-23351
For instructions and more details, see the following bulletins:
GKE security bulletin
GDC software for VMware security bulletin
GKE on AWS security bulletin
GKE on Azure security bulletin
GDC software for bare metal security bulletin
Published: 2026-04-30
2026-05-04 Update: Added patch versions for GKE.
A vulnerability in the Linux kernel ( CVE-2026-31431 ) allows an unprivileged local attacker to write to the system page cache, potentially leading to local privilege escalation and container escape.
For instructions and more details, see the following bulletins:
GKE security bulletin
GDC software for VMware security bulletin
GKE on AWS security bulletin
GKE on Azure security bulletin
GDC software for bare metal security bulletin
Published: 2026-04-30
The following vulnerabilities were discovered in the Linux kernel that can lead to a privilege escalation on Container-Optimized OS nodes: CVE-2026-23274
For instructions and more details, see the following bulletins:
GKE security bulletin
GDC software for VMware security bulletin
GKE on AWS security bulletin
GKE on Azure security bulletin
GDC software for bare metal security bulletin
Published: 2026-04-28
The following vulnerabilities were discovered in the Linux kernel that can lead to a privilege escalation on Container-Optimized OS and Ubuntu nodes: CVE-2025-38248
For instructions and more details, see the following bulletins:
GKE security bulletin
GDC software for VMware security bulletin
GKE on AWS security bulletin
GKE on Azure security bulletin
GDC software for bare metal security bulletin
Published: 2026-04-28
2026-05-07 Update: Added patch versions for Ubuntu node pools on GKE
The following vulnerabilities were discovered in the Linux kernel that can lead to a privilege escalation on Container-Optimized OS nodes: CVE-2026-23074
For instructions and more details, see the following bulletins:
GKE security bulletin
GDC software for VMware security bulletin
GKE on AWS security bulletin
GKE on Azure security bulletin
GDC software for bare metal security bulletin
Published: 2026-04-16
The following vulnerabilities were discovered in the Linux kernel that can lead to a privilege escalation on Container-Optimized OS nodes: CVE-2026-23209
For instructions and more details, see the following bulletins:
GKE security bulletin
GDC software for VMware security bulletin
GKE on AWS security bulletin
GKE on Azure security bulletin
GDC software for bare metal security bulletin
Published: 2026-04-14
AMD reported a vulnerability in its firmware that could have allowed a malicious hypervisor to direct the IOMMU to write into the guest memory of AMD SEV-SNP enabled instances, compromising guest data integrity. Google rolled out a mitigation to vulnerable Confidential VM instances with AMD SEV-SNP enabled.
No customer action is needed. The mitigation has already been applied to Confidential VM instances with AMD SEV-SNP enabled.
For more information, see AMD advisory AMD-SB-3016 .
Published: 2026-04-14
The following vulnerabilities were discovered in the Linux kernel that can lead to a privilege escalation on Container-Optimized OS nodes: CVE-2026-23231
For instructions and more details, see the following bulletins:
GKE security bulletin
GDC software for VMware security bulletin
GKE on AWS security bulletin
GKE on Azure security bulletin
GDC software for bare metal security bulletin
Published: 2026-04-14
Resear...
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
