ChromeOS LTS 150 Update Includes 62 Listed Security Fixes
Tech GuruQuick Answer
Check LTS-150 device eligibility and deploy 150.0.7871.289 with platform 16700.70.0 when offered. Restart devices and verify both version identifiers, policies and representative managed workloads.
Confirm Scope And Apply The Supported Remediation
What to do now: Record device models, LTS channel, Chrome and platform versions, update eligibility, policy and owner. Confirm LTS-150 and whether the device is offered the new build. The announcement applies to most devices; it does not establish availability for every model. Use supported ChromeOS device management and the official update mechanism. Schedule required restarts and retain exceptions for devices awaiting availability. Verify the Chrome and platform versions after restart; test sign-in, managed applications, networking, printing and peripherals relevant to each device group.
Last verified: 2026-11-12 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | ChromeOS devices on the LTS-150 channel |
|---|---|
| Advisory | ChromeOS-LTS-150.0.7871.289 |
| CVEs | CVE-2026-106269, CVE-2026-110167, CVE-2026-110170, CVE-2026-110917, CVE-2026-113012, CVE-2026-113020, CVE-2026-113040, CVE-2026-113095, CVE-2026-113154, CVE-2026-113161, CVE-2026-113303, CVE-2026-113309, CVE-2026-113310, CVE-2026-113336, CVE-2026-118304, CVE-2026-118306, CVE-2026-118307, CVE-2026-118308, CVE-2026-118311, CVE-2026-118315, CVE-2026-118317, CVE-2026-118318, CVE-2026-118331, CVE-2026-118332, CVE-2026-118334, CVE-2026-118337, CVE-2026-118339, CVE-2026-118341, CVE-2026-118342, CVE-2026-118343, CVE-2026-118344, CVE-2026-118346, CVE-2026-118347, CVE-2026-118349, CVE-2026-118353, CVE-2026-118356, CVE-2026-118357, CVE-2026-118358, CVE-2026-119260, CVE-2026-119265, CVE-2026-119266, CVE-2026-119267, CVE-2026-119270, CVE-2026-121061, CVE-2026-121076, CVE-2026-121119, CVE-2026-121182, CVE-2026-121211, CVE-2026-121213, CVE-2026-126856, CVE-2026-126859, CVE-2026-126863, CVE-2026-126869, CVE-2026-126879, CVE-2026-126887, CVE-2026-126901, CVE-2026-76024, CVE-2026-76029, CVE-2026-76031, CVE-2026-87480, CVE-2026-87651, CVE-2026-91718 |
| Authoritative release date | November 11, 2026 at 23:06:31 UTC, from the official Chrome feed. |
| Authority revision date | No separate revision date is provided by the authority. |
| Affected versions | LTS-150 devices pending the announced security update. Google describes rollout to most ChromeOS devices and does not provide per-CVE introduction versions. |
| Fixed version | ChromeOS LTS 150.0.7871.289, platform version 16700.70.0 |
| CVSS base score | Not provided by the authority |
| CVSS severity | Critical (highest vendor rating; 6 Critical and 56 High listed fixes) |
| Exploitation status | Google does not state exploitation of these issues in this update post.; no exploitation claim is inferred. |
What Changed
Google rolls out a new LTS-150 build with 62 enumerated security fixes, including critical memory-safety and input-validation issues. The list is described as selected fixes.
What To Validate Now
- Inventory. Record device models, LTS channel, Chrome and platform versions, update eligibility, policy and owner.
- Establish applicability. Confirm LTS-150 and whether the device is offered the new build. The announcement applies to most devices; it does not establish availability for every model.
- Remediate. Use supported ChromeOS device management and the official update mechanism. Schedule required restarts and retain exceptions for devices awaiting availability.
- Validate. Verify the Chrome and platform versions after restart; test sign-in, managed applications, networking, printing and peripherals relevant to each device group.
- 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
Respect the approved LTS channel and device support lifecycle. Stage operational testing and preserve deployment evidence; the listed severity ratings are not a statement of active 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.
