Google Chrome 154 Stable Update Fixes Eleven Vulnerabilities
Tech GuruQuick Answer
Google completed its Chrome 154 Stable security release details for desktop and confirmed the same security fixes in the Android build. The notices list eleven CVEs with Google ratings from Critical to Medium but no CVSS base scores. Update each platform to its supported fixed build.
Confirm Scope And Apply The Supported Fix
What to do now: Inventory Chrome by platform, deploy the applicable Chrome 154 Stable build, confirm the running version after relaunch, validate managed policies and extensions, and retain change evidence.
Last verified: 2026-10-03 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | Google Chrome Stable for desktop and Android |
|---|---|
| Advisory | Chrome 154 Stable Desktop 2026-10-01 / Chrome 154 Stable Android 2026-10-01 |
| CVEs | CVE-2026-103621, CVE-2026-103622, CVE-2026-103623, CVE-2026-103624, CVE-2026-103625, CVE-2026-103626, CVE-2026-103627, CVE-2026-103628, CVE-2026-103629, CVE-2026-103630, CVE-2026-103631 |
| Authoritative release date | 2026-10-02 01:04:35 UTC (desktop Stable release-feed publication) |
| Authority revision date | 2026-10-02 16:07:45 UTC (desktop notice completed with vulnerability details); Android Stable notice was verified separately |
| Affected versions | Desktop Chrome releases before 154.0.8037.97 on Linux and before 154.0.8037.97/.98 on Windows and macOS; Android Chrome releases before 154.0.8037.126. |
| Fixed version | Chrome 154.0.8037.97/.98 for Windows and macOS / 154.0.8037.97 for Linux / 154.0.8037.126 for Android |
| CVSS base score | Not provided by the authority |
| CVSS severity | Not provided by the authority |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
Google completed the Chrome 154 Stable security details with eleven CVEs: one Google-rated Critical issue, nine High issues, and one Medium issue. Google did not publish CVSS base scores in the release notices.
What To Validate Now
- Inventory. Locate Google Chrome Stable for desktop and Android deployments, versions, enabled features, exposure paths, owners, and dependent services.
- Establish applicability. Inventory managed and unmanaged Chrome installations on Windows, macOS, Linux, and Android, and compare the exact installed version with the platform-specific fixed version. Do not apply one platform's build number to another platform.
- Remediate. Update Chrome through Google's supported Stable channel to 154.0.8037.97/.98 on Windows and macOS, 154.0.8037.97 on Linux, or 154.0.8037.126 on Android, as applicable.
- Validate. Relaunch Chrome where required, confirm the running version from the browser or managed inventory, verify update-policy and extension behavior, and retain before-and-after version and policy evidence.
- 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
Stage the browser update with business-critical extensions, kiosk workflows, and managed policies; coordinate relaunches; preserve a supported recovery path; and do not infer active exploitation from Google's severity labels.
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.
