Provider changes/Google CloudGOOGLE CLOUD · VERIFIED CHANGE

Cloud SQL for MySQL: security change

Cloud SQL requires maintenance or time-zone configuration changes to avoid one-hour errors starting November 1, 2026. Apigee hybrid warns against v1.16.12, and Container-Optimized OS includes vulnerability fixes and reduced system limits.

Verified Oct 31, 20265 official sources

Mentioned in the evidence

  • Cloud SQL for MySQL
  • Cloud SQL for PostgreSQL
  • Cloud SQL for SQL Server
  • Apigee hybrid v1.16.12
  • apigee-connect-agent original regression issue 578314600 original regression issue 578314600

Official sources

  • Google Cloud changelog (changelog) ↗
    Changed: kernel.threads-max: 63445 -> 63443
  • Google Cloud changelog (changelog) ↗
    Note: Do not use Apigee hybrid v1.16.12 due to a potential regression in apigee-connect-agent (see known issue 578314600). Use v1.16.13 instead.
  • Google Cloud changelog (changelog) ↗
    Removed the compromised emSign roots and the cross-signing Comodo AAA Services root from the system and Java (cacerts) trust stores across containers.
  • Google Cloud changelog (changelog) ↗
    Starting November 1, 2026, at 02:00 a.m. local time, unpatched Cloud SQL for MySQL instances that evaluate certain local Canadian time zones (across Alberta, British Columbia, Manitoba, and Northwest Territories) will lag by one hour because the instances still follow the
  • Google Cloud changelog (changelog) ↗
    Fixed CVE-2026-42508, CVE-2026-39830, CVE-2026-39833 in google-osconfig-agent. Updated app-arch/brotli to 1.0.10. This resolves CVE-2026-111497. Fixed CVE-2026-98432 in the Linux kernel.

This is a global change, verified against Google Cloud’s own sources. It is not an assessment of your systems or your impact.

A global change is not your impact.

Auterim checks your confirmed dependencies and can verify repository references when GitHub is connected.