Google Cloud security bulletins
8 items in the render window (newest 100 + all corrections; not this source's all-time total) ·
status healthy · last successful fetch 2026-11-21 19:16 UTC
Feed for this sourceRSS
PHP session handler RCE affects Google Cloud managed runtimes
Do:Set session.upload_progress.enabled = 0 in php.ini immediately for all PHP applications.
WHAT CHANGEDGoogle 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 < 8.5.13, 8.4 < 8.4.28, 8.3 < 8.3.37, 8.2 < 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 MATTERSAn 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 DOSet 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.
Model-reported confidence 95% (not measured accuracy)
Primary source ↗
written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## GCP-2026-090 +https://docs.cloud.google.com/support/bulletins/index#gcp-2026-090 +2026-11-21T00:05:07.650246+00:00 + +Published: 2026-11-20Description + +Description +Severity +Notes + +A critical vulnerability was discovered in PHP's default file-based +session handler. This impacts the following PHP versions: + +PHP 8.5 < 8.5.13 +PHP 8.4 < 8.4.28 +PHP 8.3 < 8.3.37 +PHP 8.2 < 8.2.36 +PHP 8.1, PHP 7.2 (end of life, no fix available) + +The following Google Cloud products are impacted: + +App Engine Standard (second-generation PHP 7.2–8.5 runtimes) +App Engine Flexible +Cloud Run +Cloud Run functions + +What should I do? + +Immediate mitigation, all PHP applications + +Disable Session Upload Progress: If your +application does not require tracking upload progress, disabling +this feature in php.ini mitigates the primary +attack path for phpAfterShell (CVE-2026-126714) in particular: +session.upload_progress.enabled = 0 +Where feasible, switch PHP session storage away from local +filesystem handlers (session.save_handler = files) +to an external store such as Redis, Memcache, or a +database. + +Self-managed containers + +Cloud Run containers and App Engine flexible custom runtimes +can upgrade immediately to upstream PHP 8.2.36, 8.3.37, 8.4.28, +or 8.5.13, rebuild, and redeploy without waiting on +Google-managed runtime rollouts. + +Managed runtimes with automatic base image +updates + +Apply the Disable Session Upload Progress mitigations +above +App Engine standard (second-generation PHP 8.2–8.5) and Cloud +Run services / Cloud Run functions with automatic base image +updates enabled will receive patched PHP runtimes automatically +once published. + +Managed runtimes without automatic updates or pinned +versions: + +Apply the Disable Session Upload Progress mitigations +above +App Engine flexible (managed PHP runtime), Cloud Run jobs and +worker pools, Cloud Functions (1st gen), and deployments pinned +to a specific patch string will need to rebuild and redeploy +once Google publishes the updated runtime images. + +End-of-life PHP versions (7.2–8.1): + +No upstream patches will be released for PHP 8.1 or earlier. +Customers should upgrade to a supported PHP runtime (8.2 or +later) or apply the php.ini / non-file session +mitigations above. + +What vulnerabilities are being addressed? +Google is preparing updates for affected managed PHP runtimes and +base images, and will update this bulletin as patched images become +available. +CVE-2026-126714 is a vulnerability in PHP's default file-based +session handler (session.save_handler = files). When PHP +writes session data (for example, during unauthenticated file upload +progress tracking), the write is not atomic. If a PHP worker stops +abruptly mid-write—such as from a memory limit or request timeout—a +partially overwritten, malformed session file can remain on disk. When +a later request calls session_start(), PHP deserializes +that file; with crafted input, an unauthenticated remote attacker can +manipulate the deserialized data to execute arbitrary code. Because +this issue stems from how session files are written to disk rather +than earlier PHP request-cleanup vulnerabilities, upgrading to a +patched PHP version or applying the session mitigations above is +required. + +Critical + +CVE-2026-126714
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
| triage verdict | MATERIAL at 0.98, needed 0.55 |
|---|---|
| triage reasoning | Critical RCE in PHP session handler affecting Google Cloud managed runtimes requires immediate patching or mitigation. |
| signals | known exploitation: CVE-2026-126714 in PHP session handler · affects cloud managed runtimes: App Engine Standard, App Engine Flexible, Cloud Run, Cloud Run functions · affects customer-facing control plane: Google-managed PHP runtimes · critical severity rating · unauthenticated remote code execution · actionable mitigation and upgrade paths provided · affects runtime versions in active use (PHP 8.2–8.5) |
| suppression | — |
| triage model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | anthropic/claude-sonnet-4.5 ($0.00000) |
GKE patches CVE-2026-99288 for Container-Optimized OS 1.32 and 1.33
Do:Remediation: see bulletin https://docs.cloud.google.com/support/bulletins/index#gcp-2026-088.
WHAT CHANGEDGoogle 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 MATTERSThe 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 DORemediation: see bulletin https://docs.cloud.google.com/support/bulletins/index#gcp-2026-088.
Model-reported confidence 85% (not measured accuracy)
Primary source ↗
written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
## GCP-2026-088 https://docs.cloud.google.com/support/bulletins/index#gcp-2026-088 -2026-11-20T15:18:20.106458+00:00 +2026-11-21T00:05:07.650246+00:00 -Published: 2026-11-19Description +Published: 2026-11-19Updated: 2026-11-20Description Description Severity Notes +2026-11-20 Update: Added GKE patch +versions containing fixes for Container-Optimized OS for minor +versions 1.32 and 1.33. Patches for GKE 1.37 on +Container-Optimized OS and Ubuntu node images are still in +progress. A denial-of-service vulnerability (CVE-2026-99288) was discovered in the Linux kernel TCP implementation. The flaw can cause a kernel panic (denial of service) on the affected virtual machine; it does not allow
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
| triage verdict | MATERIAL at 0.92, needed 0.55 |
|---|---|
| triage reasoning | GKE patch versions released for kernel DoS affecting managed Kubernetes runtime customers cannot patch. |
| signals | security advisory update with new patch versions · GKE patch versions added for Container-Optimized OS 1.32 and 1.33 · affects managed Kubernetes runtime (GKE) that customers cannot patch themselves · Linux kernel TCP DoS vulnerability in cloud control plane/managed service · update timestamp and published date changed, indicating advisory evolution |
| suppression | — |
| triage model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | anthropic/claude-sonnet-4.5 ($0.00000) |
NGINX HTTP/2 vulnerabilities enable DoS and potential RCE
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) pe…
WHAT CHANGEDF5 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 MATTERSSelf-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 DOUpgrade 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: "false" 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.
Model-reported confidence 95% (not measured accuracy)
Primary source ↗
written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## GCP-2026-089 +https://docs.cloud.google.com/support/bulletins/index#gcp-2026-089 +2026-11-20T15:18:20.106458+00:00 + +Published: 2026-11-20Description + +Description +Severity +Notes + +On November 18, 2026, F5 disclosed HTTP/2 vulnerabilities +CVE-2026-123633 and CVE-2026-123007 in NGINX Open Source (1.19.7-1.31.8 +for CVE-2026-123633; 1.9.5-1.31.8 for CVE-2026-123007) and NGINX Plus, +alongside eight additional NGINX CVEs in F5's master advisory +(K000164058). +Under specific configuration and traffic conditions, an unauthenticated +remote attacker can crash an NGINX worker process (DoS) or potentially +achieve remote code execution (RCE). Google Cloud's core load balancing +and managed infrastructure (including Google Front End, Cloud Load +Balancing, GKE control plane, Cloud Run, Cloud Functions, and App +Engine) are not affected. This bulletin provides guidance for customers +operating self-managed NGINX deployments on Google Cloud. +What should I do? + +Managed Google Cloud services: No customer action +is required if you rely solely on unaffected Google Cloud managed +platforms (including Google Front End, Cloud Load Balancing, GKE +control plane, Cloud Run, Cloud Functions, and App Engine). Google +is patching any isolated Google-managed components internally, with +zero customer impact and no customer action required. +Customer-managed NGINX on Google Cloud (GKE Ingress +Controllers, Compute Engine VMs, and NGINX-based Cloud Marketplace +images): Google has also temporarily delisted affected +Google-maintained Click-to-Deploy NGINX listings on Cloud +Marketplace while patched images are being prepared. + +Patch: Upgrade NGINX Open Source to +1.31.9 +(mainline) or 1.30.7 (stable), or NGINX Plus to the latest fixed +releases (37.0.7.1 / 37.2.0.1 for CVE-2026-123633; 37.0.8.1 / +37.3.0.1 for CVE-2026-123007) in +F5 advisory K000164058 +to remediate these vulnerabilities and all November 18 F5 CVEs +(see also the +Wiz research blog). +Temporary mitigation (if unable to patch +immediately): Disable HTTP/2 on exposed NGINX listeners +(for example, set use-http2: "false" in +ingress-nginx or remove http2 listener +directives and reload), or place a Google Cloud External +Application Load Balancer in front of NGINX configured to speak +HTTP/1.1 to backends. (Note: Disabling HTTP/2 does not mitigate +non-HTTP/2 CVEs, so upgrading to a patched release remains +recommended.) + +What vulnerabilities are being addressed? + +CVE-2026-123633 (NGINX Open Source 1.19.7-1.31.8; NGINX +Plus R33+ / 37.0.0-37.2.0.0): Reentrant HTTP/2 +connection-draining heap use-after-free in +ngx_http_v2_module when reverse proxying +(proxy_pass, fastcgi_pass, +uwsgi_pass, scgi_pass, or +grpc_pass) under worker_connections +depletion, enabling worker crash (DoS) or potential remote code +execution (if ASLR is disabled or bypassed). +CVE-2026-123007 (NGINX Open Source 1.9.5-1.31.8; NGINX +Plus R33+ / 37.0.0-37.3.0.0): HTTP/2 flow-control window +vulnerability during crafted HTTP/2 traffic processing; does not +require reverse proxying and can also affect NGINX serving static +content directly over HTTP/2, enabling worker process crashes (DoS) +or potential remote code execution (if ASLR is disabled or +bypassed). +Additional F5 November 18, 2026 CVEs: +F5 master +advisory K000164058 also discloses eight additional NGINX CVEs +alongside these two primary HTTP/2 vulnerabilities; upgrading to a +patched release remediates these vulnerabilities and all November 18 +F5 CVEs. + +High + +CVE-2026-123633 +CVE-2026-123007
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
| triage verdict | MATERIAL at 0.95, needed 0.55 |
|---|---|
| triage reasoning | NGINX RCE/DoS vulnerabilities affecting customer-managed deployments on GCP require immediate patching action. |
| signals | NGINX vulnerabilities with known exploitation potential (RCE + DoS) · affects self-managed deployments on GCP (GKE Ingress, Compute Engine, Marketplace) · customer action required for non-managed NGINX · specific patch versions provided (1.31.9, 1.30.7 for Open Source; 37.0.7.1+ for Plus) · affects web framework / reverse proxy in typical dependency tree · HTTP/2 protocol vulnerabilities in widely-deployed software · temporary mitigation guidance provided |
| suppression | — |
| triage model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | anthropic/claude-sonnet-4.5 ($0.00000) |
CVE-2026-99288 kernel panic in GKE via crafted TCP packets
Do:Check whether your GKE clusters run Container-Optimized OS or Ubuntu (gVisor and Windows Server nodes are not affected).
WHAT CHANGEDGoogle 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 MATTERSBoth 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 DOCheck 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.
Model-reported confidence 95% (not measured accuracy)
Primary source ↗
written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## GCP-2026-088 +https://docs.cloud.google.com/support/bulletins/index#gcp-2026-088 +2026-11-20T02:23:07.896324+00:00 + +Published: 2026-11-19Description + +Description +Severity +Notes + +A denial-of-service vulnerability (CVE-2026-99288) was discovered in +the Linux kernel TCP implementation. The flaw can cause a kernel panic +(denial of service) on the affected virtual machine; it does not allow +privilege escalation or container breakout to code execution on the +host. A remote attacker can trigger it by sending specially crafted +TCP packets to a reachable TCP listener on a node, Pod, or the cluster +control plane's IP-based endpoint. Internal traffic within the same +VPC can also trigger this vulnerability. +GKE Standard clusters and GKE +Autopilot clusters running Container-Optimized OS or +Ubuntu prior to the patched versions are affected across both cluster +control planes and worker nodes. Pods running in GKE Sandbox +(gVisor) and Windows Server node pools are not affected. +For instructions and more details, see the +GKE security bulletin. + +High + +CVE-2026-99288
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
| triage verdict | MATERIAL at 0.92, needed 0.55 |
|---|---|
| triage reasoning | GKE control plane and worker node DoS vulnerability reachable from internal VPC requires platform lead action. |
| signals | known CVE with assigned number · affects GKE control planes and worker nodes · affects managed Kubernetes runtime that customer cannot patch · denial-of-service via network-reachable endpoint · affects standard infrastructure (Container-Optimized OS, Ubuntu) · internal VPC traffic can trigger it · high severity rating · new bulletin entry with published date |
| suppression | — |
| triage model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | anthropic/claude-sonnet-4.5 ($0.00000) |
nginx HTTP/2 RCE vulnerabilities affect Apigee Edge for Private Cloud non-default configs
Do:Check Router virtual host configurations for HTTP/2 enablement.
WHAT CHANGEDCVE-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 MATTERSA 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 DOCheck 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.
Model-reported confidence 85% (not measured accuracy)
Primary source ↗
written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## GCP-2026-087 +https://docs.cloud.google.com/support/bulletins/index#gcp-2026-087 +2026-11-20T02:23:07.896324+00:00 + +Published: 2026-11-19Description + +Description +Severity +Notes + +Two vulnerabilities in the nginx HTTP/2 module, CVE-2026-123633 and +CVE-2026-123007, can let a remote, unauthenticated attacker run code on +an nginx server that accepts HTTP/2 connections. Both are fixed in +nginx 1.30.7. +The Router in Apigee Edge for Private Cloud 4.54.00 and +4.53.01 uses an nginx version in the affected range. Routers are not +affected in the default and supported configuration, because HTTP/2 is +not supported on Router virtual hosts. +For more information, see the +Apigee security bulletin. + +Critical + +CVE-2026-123007 +CVE-2026-123633
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
| triage verdict | MATERIAL at 0.92, needed 0.55 |
|---|---|
| triage reasoning | RCE in nginx HTTP/2 affecting Apigee Edge managed service; platform leads running Apigee must verify configuration and patch. |
| signals | known RCE vulnerabilities in nginx HTTP/2 module · affects Apigee Edge for Private Cloud (managed service) · critical severity rating · remote unauthenticated attack vector · fixed version available (nginx 1.30.7) · note: default config not affected, but non-default deployments are at risk |
| suppression | — |
| triage model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | anthropic/claude-sonnet-4.5 ($0.00000) |
VMware vCenter and Cloud Foundation vulnerability affects Google Cloud VMware Engine
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 requir…
WHAT CHANGEDGoogle 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 MATTERSGoogle 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 DOCheck 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
Model-reported confidence 85% (not measured accuracy)
Primary source ↗
written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## GCP-2026-085 +https://docs.cloud.google.com/support/bulletins/index#gcp-2026-085 +2026-11-20T02:23:07.896324+00:00 + +Published: 2026-11-19Description + +Description +Severity +Notes + +According to VMware security advisory +VMSA-2026-0009, +a vulnerability was identified in VMware vCenter and VMware Cloud +Foundation (VCF). There are no known workarounds for this reported +vulnerability. +For remediation guidance and product-specific details, see the +following bulletins: + +Google Cloud VMware Engine security bulletin +VMware solution on Google Cloud security bulletin + +Critical + +VMSA-2026-0009 +CVE-2026-123890
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
| triage verdict | MATERIAL at 0.92, needed 0.55 |
|---|---|
| triage reasoning | Critical VMware vulnerability in Google Cloud managed service requires platform lead action. |
| signals | critical severity rating · known vulnerability in VMware vCenter and VMware Cloud Foundation · no known workarounds · affects Google Cloud managed service (VMware Engine) · customer cannot patch — managed runtime responsibility · new advisory entry with remediation guidance |
| suppression | — |
| triage model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | anthropic/claude-sonnet-4.5 ($0.00000) |
GCP-2026-078 updated with GKE patch versions for CVE-2026-98432
Do:Check your GKE cluster versions against the patched versions listed in the bulletin.
WHAT CHANGEDGoogle 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 MATTERSGKE 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 DOCheck 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.
Model-reported confidence 95% (not measured accuracy)
Primary source ↗
written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
## GCP-2026-078 https://docs.cloud.google.com/support/bulletins/index#gcp-2026-078 -2026-11-17T22:03:33.418511+00:00 +2026-11-18T16:05:50.977460+00:00 -Published: 2026-11-04Description +Published: 2026-11-04Updated: 2026-11-18Description Description Severity Notes +2026-11-18 Update: Added patch versions for GKE. 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
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
| triage verdict | MATERIAL at 0.92, needed 0.55 |
|---|---|
| triage reasoning | GKE patch versions added for kernel vulnerability enabling container escape. Platform leads must patch this week. |
| signals | advisory updated with new patch versions · GKE (managed Kubernetes) affected — cloud control plane component · container escape and root code execution described · Linux kernel vulnerability in TCP stack · patch versions now available (previously absent) |
| suppression | — |
| triage model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | anthropic/claude-sonnet-4.5 ($0.00000) |
Corrections and arithmetic notes
CORRECTED Application Integration privilege escalation patched August 27
CORRECTED 2026-10-15 01:38 UTC — CORRECTION: Google's GCP-2026-068 bulletin states that CVE-2026-85298 in Application Integration was patched on August 27, 2026 and that no customer action is required. RADAR's ACTION NEEDED / VERIFY_EXPOSURE framing, the triage claim that platform leads must verify patch status, and the mandatory historical Cloud Audit Logs review in WHAT TO DO went beyond the source and should not be treated as Google requirements. Google requires no customer patch-status verification or historical log review for this bulletin. Optional RADAR defense-in-depth advice: teams with a specific concern about past service account misuse may choose to review relevant Cloud Audit Logs under their own security procedures. This optional advice is RADAR's, not Google's. The original article and source evidence are retained below as the historical record.
Google Cloud security bulletins · published 2026-10-14 17:13 UTC · corrected 2026-10-15 01:38 UTC · stood 8h 25m · cause writer overreach
WHAT CHANGED (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.
Original text (as first published, superseded)
WHY IT MATTERSAn authenticated attacker could have gained service account credentials in your Google Cloud project, bypassing intended access controls. Google rates this critical severity.
WHAT TO DOVerify 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.