<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>RADAR — Google Cloud security bulletins</title>
    <link>https://radar.trulysovereign.com</link>
    <atom:link href="https://radar.trulysovereign.com/feeds/source/google-cloud-security-bulletins.xml" rel="self" type="application/rss+xml"/>
    <description>Changes RADAR detected at Google Cloud security bulletins.</description>
    <language>en</language>
    <lastBuildDate>Sat, 21 Nov 2026 19:19:18 GMT</lastBuildDate>
    <item>
      <title>PHP session handler RCE affects Google Cloud managed runtimes</title>
      <link>https://radar.trulysovereign.com/items/920bda9c-f160-4530-8c20-8f4c7d7a4c0e</link>
      <guid isPermaLink="false">920bda9c-f160-4530-8c20-8f4c7d7a4c0e</guid>
      <pubDate>Sat, 21 Nov 2026 19:18:06 GMT</pubDate>
      <category>mitigate</category>
      <source url="https://docs.cloud.google.com/support/bulletins/index#gcp-2026-090">Google Cloud security bulletins</source>
      <description>Google published GCP-2026-090 on 2026-11-20, disclosing CVE-2026-126714, a critical unauthenticated remote code execution vulnerability in PHP's file-based session handler. Affected versions are PHP 8.5 &lt; 8.5.13, 8.4 &lt; 8.4.28, 8.3 &lt; 8.3.37, 8.2 &lt; 8.2.36, and end-of-life 8.1 and 7.2. Impacted Google Cloud products are App Engine Standard (second-generation PHP 7.2–8.5 runtimes), App Engine Flexible, Cloud Run, and Cloud Run functions.

Why it matters: An attacker can execute arbitrary code without authentication by triggering a partial session file write (via memory limit or timeout during upload progress tracking) and then deserializing the malformed file on a subsequent request. This affects all PHP applications using the default file-based session handler on Google-managed runtimes.

What to do: Set session.upload_progress.enabled = 0 in php.ini immediately for all PHP applications. For self-managed containers on Cloud Run or App Engine Flexible custom runtimes, upgrade to PHP 8.2.36, 8.3.37, 8.4.28, or 8.5.13, rebuild, and redeploy. For managed runtimes with automatic base image updates, apply the php.ini mitigation and wait for Google's patched runtime rollout. For pinned versions or runtimes without automatic updates, apply the mitigation and rebuild once Google publishes updated images. For PHP 8.1 or earlier, upgrade to PHP 8.2+ or apply the php.ini mitigation, as no upstream patches will be released.</description>
    </item>
    <item>
      <title>GKE patches CVE-2026-99288 for Container-Optimized OS 1.32 and 1.33</title>
      <link>https://radar.trulysovereign.com/items/0ad8c973-9170-4755-9319-f592f756d3f2</link>
      <guid isPermaLink="false">0ad8c973-9170-4755-9319-f592f756d3f2</guid>
      <pubDate>Sat, 21 Nov 2026 19:17:51 GMT</pubDate>
      <category>patch_now</category>
      <source url="https://docs.cloud.google.com/support/bulletins/index#gcp-2026-088">Google Cloud security bulletins</source>
      <description>Google added GKE patch versions for Container-Optimized OS minor versions 1.32 and 1.33 to bulletin GCP-2026-088 on 2026-11-20. The patches address CVE-2026-99288, a Linux kernel TCP denial-of-service vulnerability that can cause kernel panic. Patches for GKE 1.37 on Container-Optimized OS and Ubuntu node images remain in progress.

Why it matters: The vulnerability can crash affected virtual machines through a kernel panic. GKE clusters running Container-Optimized OS on versions 1.32 or 1.33 are now patchable; clusters on 1.37 or Ubuntu remain exposed until those patches release.

What to do: Remediation: see bulletin https://docs.cloud.google.com/support/bulletins/index#gcp-2026-088.</description>
    </item>
    <item>
      <title>NGINX HTTP/2 vulnerabilities enable DoS and potential RCE</title>
      <link>https://radar.trulysovereign.com/items/24c15b5a-7949-468d-bd4d-f3576f81e225</link>
      <guid isPermaLink="false">24c15b5a-7949-468d-bd4d-f3576f81e225</guid>
      <pubDate>Fri, 20 Nov 2026 20:23:17 GMT</pubDate>
      <category>patch_now</category>
      <source url="https://docs.cloud.google.com/support/bulletins/index#gcp-2026-089">Google Cloud security bulletins</source>
      <description>F5 disclosed CVE-2026-123633 and CVE-2026-123007 on 18 November 2026, affecting NGINX Open Source 1.19.7-1.31.8 and 1.9.5-1.31.8 respectively, and NGINX Plus R33+. Under specific conditions, an unauthenticated remote attacker can crash NGINX worker processes or potentially achieve remote code execution. CVE-2026-123633 requires reverse proxying and worker connection depletion; CVE-2026-123007 affects HTTP/2 traffic including static content serving. Google Cloud managed services (Cloud Load Balancing, GKE control plane, Cloud Run, Cloud Functions, App Engine) are not affected.

Why it matters: Self-managed NGINX deployments on GCP — GKE Ingress controllers, Compute Engine VMs, and Marketplace images — are exposed to remote DoS and potential RCE if serving HTTP/2 traffic. The RCE risk increases if ASLR is disabled or bypassed. Google has delisted affected Click-to-Deploy NGINX Marketplace images until patched versions are available.

What to do: Upgrade NGINX Open Source to 1.31.9 (mainline) or 1.30.7 (stable), or NGINX Plus to 37.0.7.1/37.2.0.1 (for CVE-2026-123633) or 37.0.8.1/37.3.0.1 (for CVE-2026-123007) per F5 advisory K000164058. If immediate patching is not possible, disable HTTP/2 on exposed NGINX listeners (set use-http2: &quot;false&quot; in ingress-nginx or remove http2 listener directives) or place a Google Cloud External Application Load Balancer configured for HTTP/1.1 to backends in front of NGINX. Note that disabling HTTP/2 does not mitigate the eight additional November 18 F5 CVEs, so upgrading remains necessary.</description>
    </item>
    <item>
      <title>CVE-2026-99288 kernel panic in GKE via crafted TCP packets</title>
      <link>https://radar.trulysovereign.com/items/a8b2921f-a32e-4faf-b9cb-9c1d5d7517ef</link>
      <guid isPermaLink="false">a8b2921f-a32e-4faf-b9cb-9c1d5d7517ef</guid>
      <pubDate>Fri, 20 Nov 2026 07:18:29 GMT</pubDate>
      <category>patch_now</category>
      <source url="https://docs.cloud.google.com/support/bulletins/index#gcp-2026-088">Google Cloud security bulletins</source>
      <description>Google published GCP-2026-088 on 2026-11-19 for CVE-2026-99288, a denial-of-service vulnerability in the Linux kernel TCP implementation affecting GKE Standard and Autopilot clusters running Container-Optimized OS or Ubuntu. A remote attacker can trigger a kernel panic by sending specially crafted TCP packets to any reachable TCP listener on a node, Pod, or control plane IP endpoint. Internal VPC traffic can also trigger it.

Why it matters: Both control planes and worker nodes are vulnerable to remote denial-of-service from any network position that can reach a TCP listener, including from within the same VPC. The cluster control plane itself is a reachable target. Affected nodes will kernel panic, taking down running workloads.

What to do: Check whether your GKE clusters run Container-Optimized OS or Ubuntu (gVisor and Windows Server nodes are not affected). Remediation: see bulletin https://docs.cloud.google.com/support/bulletins/index#gcp-2026-088. The full article could not be retrieved (attempted 2026-11-20T07:18:20.598Z); this item uses the feed entry only.</description>
    </item>
    <item>
      <title>nginx HTTP/2 RCE vulnerabilities affect Apigee Edge for Private Cloud non-default configs</title>
      <link>https://radar.trulysovereign.com/items/e3c0b8e9-6a29-40ef-86aa-988e9a77fb5f</link>
      <guid isPermaLink="false">e3c0b8e9-6a29-40ef-86aa-988e9a77fb5f</guid>
      <pubDate>Fri, 20 Nov 2026 07:18:18 GMT</pubDate>
      <category>verify_exposure</category>
      <source url="https://docs.cloud.google.com/support/bulletins/index#gcp-2026-087">Google Cloud security bulletins</source>
      <description>CVE-2026-123633 and CVE-2026-123007 were published on 2026-11-19, affecting nginx HTTP/2 module versions before 1.30.7. Apigee Edge for Private Cloud versions 4.54.00 and 4.53.01 use an affected nginx version. Default configurations are not vulnerable because HTTP/2 is not supported on Router virtual hosts, but non-default deployments that enable HTTP/2 are exposed to remote unauthenticated code execution.

Why it matters: A remote attacker can execute code on Apigee Routers configured to accept HTTP/2 connections without authentication. Default installations are safe, but any Router with HTTP/2 explicitly enabled on a virtual host is exploitable.

What to do: Check Router virtual host configurations for HTTP/2 enablement. If running default configuration, no action required. Remediation: see bulletin https://docs.cloud.google.com/support/bulletins/index#gcp-2026-087.</description>
    </item>
    <item>
      <title>VMware vCenter and Cloud Foundation vulnerability affects Google Cloud VMware Engine</title>
      <link>https://radar.trulysovereign.com/items/dd1239c5-1629-45b3-aaa2-2b2f8b713d9b</link>
      <guid isPermaLink="false">dd1239c5-1629-45b3-aaa2-2b2f8b713d9b</guid>
      <pubDate>Fri, 20 Nov 2026 07:18:06 GMT</pubDate>
      <category>verify_exposure</category>
      <source url="https://docs.cloud.google.com/support/bulletins/index#gcp-2026-085">Google Cloud security bulletins</source>
      <description>Google Cloud published security bulletin GCP-2026-085 on 2026-11-19, referencing VMware security advisory VMSA-2026-0009. The advisory identifies CVE-2026-123890, a critical severity vulnerability in VMware vCenter and VMware Cloud Foundation with no known workarounds.

Why it matters: Google Cloud VMware Engine and VMware solution on Google Cloud are managed services running the affected VMware components. Customers cannot patch these managed runtimes directly and must rely on Google Cloud to apply remediation.

What to do: Check the Google Cloud VMware Engine security bulletin and VMware solution on Google Cloud security bulletin linked in GCP-2026-085 for remediation status and any required customer actions. Remediation: see bulletin https://docs.cloud.google.com/support/bulletins/index#gcp-2026-085</description>
    </item>
    <item>
      <title>GCP-2026-078 updated with GKE patch versions for CVE-2026-98432</title>
      <link>https://radar.trulysovereign.com/items/5a72809d-808b-43f0-a41f-0b10be98ed3b</link>
      <guid isPermaLink="false">5a72809d-808b-43f0-a41f-0b10be98ed3b</guid>
      <pubDate>Wed, 18 Nov 2026 20:34:58 GMT</pubDate>
      <category>patch_now</category>
      <source url="https://docs.cloud.google.com/support/bulletins/index#gcp-2026-078">Google Cloud security bulletins</source>
      <description>Google Cloud security bulletin GCP-2026-078 was updated on 2026-11-18 to add patch versions for GKE. The bulletin covers CVE-2026-98432, a Linux kernel IPv4 TCP stack vulnerability that can cause kernel panic or container escape with root code execution on the node, exploitable by an unprivileged process.

Why it matters: GKE clusters running unpatched versions are exposed to container escape attacks. An attacker with unprivileged access inside a container can execute code as root on the underlying node, breaking container isolation and potentially compromising the entire cluster.

What to do: Check your GKE cluster versions against the patched versions listed in the bulletin. Remediation: see bulletin https://docs.cloud.google.com/support/bulletins/index#gcp-2026-078 Remediation: see bulletin https://docs.cloud.google.com/support/bulletins/index#gcp-2026-078.</description>
    </item>
    <item>
      <title>[CORRECTED] Application Integration privilege escalation patched August 27</title>
      <link>https://radar.trulysovereign.com/items/2fc4875b-00de-47c3-b58e-883d213e40eb</link>
      <guid isPermaLink="false">2fc4875b-00de-47c3-b58e-883d213e40eb</guid>
      <pubDate>Wed, 14 Oct 2026 17:13:41 GMT</pubDate>
      <category>verify_exposure</category>
      <category>corrected</category>
      <source url="https://docs.cloud.google.com/support/bulletins/index#gcp-2026-068">Google Cloud security bulletins</source>
      <description>[CORRECTED] Google patched CVE-2026-85298 in Application Integration on August 27, 2026. The vulnerability allowed authenticated users to escalate privileges and impersonate service accounts through incorrect authorization in AuthConfig validation and integration execution runtime.

Why it matters: Before Google's August 27, 2026 fix, an authenticated user could escalate privileges and impersonate a service account in a Google Cloud project using Application Integration. Google rates the issue Critical and has already patched it; Google states no customer action is required.

What to do: No customer action is required: Google patched CVE-2026-85298 on August 27, 2026. Optional, RADAR's suggestion rather than a Google requirement: if you have a specific concern about past service account misuse, review the relevant Cloud Audit Logs under your own security procedures.

Original text (as first published, superseded):

WHY IT MATTERS: An authenticated attacker could have gained service account credentials in your Google Cloud project, bypassing intended access controls. Google rates this critical severity.

WHAT TO DO: Verify that no unauthorized service account activity occurred between your first use of Application Integration and August 27, 2026. Review Cloud Audit Logs for unexpected impersonation events or privilege escalations in projects using Application Integration.</description>
    </item>
  </channel>
</rss>
