Chrome Stable and Extended Stable Updates Fix Critical Flaws

P1 — VALIDATE AND UPDATEMedium to Critical · Not provided by the authorityEXPLOITATION: NOT STATED

Quick Answer

Google released Chrome Stable 155.0.8059.84/.85, Extended Stable 152.0.7977.169, and Chrome for Android 155.0.8059.84 with security fixes rated Medium through Critical. Complete the correct channel rollout, restart browsers, confirm versions, validate policy and extensions, and retain evidence.

Confirm Scope And Apply The Supported Remediation

What to do now: Inventory Chrome by platform and Stable or Extended Stable channel, force or monitor the supported update, restart browsers to load the fixed build, confirm resulting versions, and validate enterprise policy, extensions, authentication, and critical web applications.

Open the authoritative advisory

Last verified: 2026-10-16 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeGoogle Chrome Stable on Windows, macOS, Linux, and Android and Extended Stable on Windows and macOS
AdvisoryChrome Stable 155.0.8059.84/.85 / Chrome Extended Stable 152.0.7977.169 / Chrome for Android 155.0.8059.84
CVEsCVE-2026-110144, CVE-2026-110151, CVE-2026-110159, CVE-2026-110166, CVE-2026-110172, CVE-2026-110913, CVE-2026-110914, CVE-2026-110915, CVE-2026-110916, CVE-2026-110917, CVE-2026-110918, CVE-2026-110919, CVE-2026-110920, CVE-2026-110921, CVE-2026-110922
Authoritative release date2026-10-15 20:50:35.703 UTC
Authority revision date2026-10-15 23:00:00 UTC
Affected versionsChrome builds before Stable 155.0.8059.84/.85 on Windows and macOS, 155.0.8059.84 on Linux and Android, or Extended Stable 152.0.7977.169 on Windows and macOS.
Fixed versionChrome Stable 155.0.8059.84/.85 on Windows and macOS, 155.0.8059.84 on Linux and Android, or Extended Stable 152.0.7977.169 on Windows and macOS
CVSS base scoreNot provided by the authority
CVSS severityMedium to Critical
Exploitation statusNot stated by the authority; no exploitation claim is inferred.

What Changed

Google released ten Stable security fixes, including one Critical and six High vulnerabilities, and ten Extended Stable fixes, including two Critical vulnerabilities. The Android release carries the corresponding Desktop security fixes.

What To Validate Now

  1. Inventory. Locate Google Chrome Stable on Windows, macOS, Linux, and Android and Extended Stable on Windows and macOS deployments, versions, enabled features, exposure paths, owners, and dependent services.
  2. Establish applicability. Compare each deployment with the authority's affected-version statement: Chrome builds before Stable 155.0.8059.84/.85 on Windows and macOS, 155.0.8059.84 on Linux and Android, or Extended Stable 152.0.7977.169 on Windows and macOS. Do not infer applicability from product family or severity alone.
  3. Remediate. Apply Chrome Stable 155.0.8059.84/.85 on Windows and macOS, 155.0.8059.84 on Linux and Android, or Extended Stable 152.0.7977.169 on Windows and macOS through the supported vendor or project channel, following the current advisory and change-control requirements.
  4. Validate. Confirm the resulting version or managed-service state, exercise representative functionality and recovery paths, monitor for regressions, and document exceptions.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

Stable and Extended Stable require different target builds, while Android inherits the corresponding Desktop fixes. Google may keep issue details restricted during rollout; do not use Beta-channel announcements as production remediation. Preserve the authority snapshot, asset and owner records, before-and-after versions, change approval, installation output, validation results, exceptions, and rollback evidence.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.