Google Chrome 154 Stable Fixes Thirty-Two Security Vulnerabilities
Tech GuruQuick Answer
The authority published Chrome 154 Stable Desktop 2026-09-29 for Google Chrome Stable for Windows, macOS, and Linux. Google released Chrome 154 Stable for desktop with thirty-two security fixes, including one Critical ANGLE buffer overflow and High-severity V8, GPU, WebGPU, WebUI, media, Bluetooth, password, view, and authorization issues. Affected deployments should be matched to the authority's exact scope and moved to the supported fixed release.
Confirm Scope And Apply The Supported Fix
What to do now: Inventory Google Chrome Stable for Windows, macOS, and Linux, match the exact affected release or feature, apply the authority-supported fixed build or service remediation, validate the dependent workflow, and preserve evidence.
Last verified: 2026-10-01 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | Google Chrome Stable for Windows, macOS, and Linux |
|---|---|
| Advisory | Chrome 154 Stable Desktop 2026-09-29 |
| CVEs | CVE-2026-102299, CVE-2026-102300, CVE-2026-102301, CVE-2026-102302, CVE-2026-102303, CVE-2026-102304, CVE-2026-102305, CVE-2026-102306, CVE-2026-102307, CVE-2026-102308, CVE-2026-102309, CVE-2026-102310, CVE-2026-102311, CVE-2026-102312, CVE-2026-102313, CVE-2026-102314, CVE-2026-102315, CVE-2026-102316, CVE-2026-102317, CVE-2026-102318, CVE-2026-102319, CVE-2026-102320, CVE-2026-102321, CVE-2026-102323, CVE-2026-102324, CVE-2026-102325, CVE-2026-102326, CVE-2026-102327, CVE-2026-102328, CVE-2026-102329, CVE-2026-102330, CVE-2026-102331 |
| Authoritative release date | 2026-09-29 18:38:51.470 UTC |
| Authority revision date | 2026-09-29 18:38:51.470 UTC |
| Affected versions | Chrome desktop builds before 154.0.8037.92 on Windows, macOS, and Linux, plus the macOS and Windows branch before 154.0.8037.93 where that build is delivered. |
| Fixed version | Chrome 154.0.8037.92 or 154.0.8037.93 as provided for the operating system |
| CVSS base score | Not provided by the authority |
| CVSS severity | Critical to Low |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
Google released Chrome 154 Stable for desktop with thirty-two security fixes, including one Critical ANGLE buffer overflow and High-severity V8, GPU, WebGPU, WebUI, media, Bluetooth, password, view, and authorization issues.
What To Validate Now
- Inventory. Locate Google Chrome Stable for Windows, macOS, and Linux deployments, versions, enabled features, exposure paths, owners, and dependent services.
- Establish applicability. Compare each deployment with the authority's affected-version statement: Chrome desktop builds before 154.0.8037.92 on Windows, macOS, and Linux, plus the macOS and Windows branch before 154.0.8037.93 where that build is delivered. Do not infer applicability from product family or severity alone.
- Remediate. Apply Chrome 154.0.8037.92 or 154.0.8037.93 as provided for the operating system through the supported vendor or project channel, following the current advisory and change-control requirements.
- Validate. Confirm the resulting version or managed-service state, exercise representative functionality and recovery paths, monitor for regressions, and document exceptions.
- 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
Use the exact supported release stream and repository. Test dependencies, clusters, integrations, and rollback before broad deployment; a CVSS rating or reachable feature is not evidence of exploitation.
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.
