Google Chrome 156.0.8078.73/.74 Fixes 52 Security Flaws
Tech GuruQuick Answer
Google Chrome 156.0.8078.73/.74 fixes 52 security issues on desktop platforms. Inventory managed and unmanaged browsers, confirm rollout availability, update through supported controls, restart where required, validate policy and critical applications, and retain fleet evidence.
Confirm Scope And Apply The Supported Remediation
What to do now: Inventory Chrome Stable on Windows, macOS, and Linux, exact versions, update policy and management state, user populations, extensions, kiosk systems, owners, and offline devices. Match each browser to the platform-specific fixed build and Stable channel; do not apply these build numbers to ChromeOS, Android, iOS, Beta, or other channels. Deploy the platform-appropriate 156.0.8078.73/.74 build through supported Chrome update controls as Google's staged rollout reaches eligible systems. Confirm the active browser version after restart, verify enterprise policy and extension state, test authentication and critical web applications, track devices that have not received the build, and retain fleet and change evidence.
Last verified: 2026-10-28 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 156 Stable 156.0.8078.73/.74 |
| CVEs | CVE-2026-118304, CVE-2026-118305, CVE-2026-118306, CVE-2026-118307, CVE-2026-118308, CVE-2026-118309, CVE-2026-118310, CVE-2026-118311, CVE-2026-118312, CVE-2026-118313, CVE-2026-118314, CVE-2026-118315, CVE-2026-118316, CVE-2026-118317, CVE-2026-118318, CVE-2026-118319, CVE-2026-118320, CVE-2026-118321, CVE-2026-118322, CVE-2026-118327, CVE-2026-118328, CVE-2026-118329, CVE-2026-118330, CVE-2026-118331, CVE-2026-118332, CVE-2026-118333, CVE-2026-118334, CVE-2026-118335, CVE-2026-118336, CVE-2026-118337, CVE-2026-118338, CVE-2026-118339, CVE-2026-118340, CVE-2026-118341, CVE-2026-118342, CVE-2026-118343, CVE-2026-118344, CVE-2026-118345, CVE-2026-118346, CVE-2026-118347, CVE-2026-118348, CVE-2026-118349, CVE-2026-118350, CVE-2026-118351, CVE-2026-118352, CVE-2026-118353, CVE-2026-118354, CVE-2026-118355, CVE-2026-118356, CVE-2026-118357, CVE-2026-118358, CVE-2026-118359 |
| Authoritative release date | 2026-10-27 20:29:34.967 UTC |
| Authority revision date | 2026-10-27 23:02:38.722 UTC |
| Affected versions | Chrome Stable builds before 156.0.8078.73/.74 on Windows and macOS and before 156.0.8078.73 on Linux, subject to Google's staged rollout. |
| Fixed version | Chrome 156.0.8078.73/.74 on Windows and macOS; Chrome 156.0.8078.73 on Linux |
| CVSS base score | Not provided by the authority |
| CVSS severity | Medium to Critical |
| Exploitation status | Google does not state in this release that the listed vulnerabilities are being maliciously exploited.; no exploitation claim is inferred. |
What Changed
Google updated Chrome Stable with 52 security fixes, including authority-rated Critical, High, and Medium memory-corruption, use-after-free, access-control, and input-validation issues.
What To Validate Now
- Inventory. Inventory Chrome Stable on Windows, macOS, and Linux, exact versions, update policy and management state, user populations, extensions, kiosk systems, owners, and offline devices.
- Establish applicability. Match each browser to the platform-specific fixed build and Stable channel; do not apply these build numbers to ChromeOS, Android, iOS, Beta, or other channels.
- Remediate. Deploy the platform-appropriate 156.0.8078.73/.74 build through supported Chrome update controls as Google's staged rollout reaches eligible systems.
- Validate. Confirm the active browser version after restart, verify enterprise policy and extension state, test authentication and critical web applications, track devices that have not received the build, and retain fleet and change 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
Google publishes severity labels but no CVSS base scores in this release. A staged rollout can make the fixed build temporarily unavailable; do not force an unsupported channel change.
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.
