Google Chrome 158 Security Update Covers Desktop and Android

P1 — VALIDATE AND UPDATECritical · Not provided by the authorityEXPLOITATION: NOT STATED

Quick Answer

Deploy the platform-specific Chrome 158 Stable builds and verify active browser versions after restart, including managed Android devices.

Confirm Scope And Apply The Supported Remediation

What to do now: Identify installed and running browser versions, update policies, rollout holds and platform owners. Match the Stable channel and platform. Extended Stable and ChromeOS have separate announcements; do not apply these build numbers to them. Use supported Chrome update channels and managed deployment tooling. Confirm Android availability through Google Play and resolve policy blocks that prevent the approved update. Verify the running build after restart and exercise enterprise authentication, extensions, media and graphics workflows. Retain inventory, deployment and exception evidence.

Open the authoritative advisory

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

Scope And Authority

Product scopeChrome Stable on Windows, macOS, Linux and Android
AdvisoryChrome-158-Stable-2026-11-17
CVEsCVE-2026-121101, CVE-2026-130904, CVE-2026-130905, CVE-2026-130906, CVE-2026-130907, CVE-2026-130908, CVE-2026-130909, CVE-2026-130910, CVE-2026-130911, CVE-2026-130912, CVE-2026-130913, CVE-2026-130914, CVE-2026-130915, CVE-2026-130916, CVE-2026-130917, CVE-2026-130918, CVE-2026-130919, CVE-2026-130920, CVE-2026-130921, CVE-2026-130922, CVE-2026-130923, CVE-2026-130924, CVE-2026-130925, CVE-2026-130926, CVE-2026-130927, CVE-2026-130928, CVE-2026-130929, CVE-2026-130930, CVE-2026-130931, CVE-2026-130932, CVE-2026-130933, CVE-2026-130934, CVE-2026-130935, CVE-2026-130936, CVE-2026-130937, CVE-2026-130938, CVE-2026-130939, CVE-2026-130940, CVE-2026-130941, CVE-2026-130942, CVE-2026-130943, CVE-2026-130944, CVE-2026-130945, CVE-2026-130946, CVE-2026-130947, CVE-2026-130948, CVE-2026-130949, CVE-2026-130950, CVE-2026-130951, CVE-2026-130952, CVE-2026-130953, CVE-2026-130954, CVE-2026-130955, CVE-2026-130956, CVE-2026-130957, CVE-2026-130958, CVE-2026-130959, CVE-2026-130960, CVE-2026-130961, CVE-2026-130962, CVE-2026-130963, CVE-2026-130964, CVE-2026-130965, CVE-2026-130966, CVE-2026-130967, CVE-2026-130968, CVE-2026-130969, CVE-2026-130970, CVE-2026-130971, CVE-2026-130972, CVE-2026-130973, CVE-2026-130974, CVE-2026-130975, CVE-2026-130976, CVE-2026-130977, CVE-2026-130978, CVE-2026-130979, CVE-2026-130980, CVE-2026-130981, CVE-2026-130982, CVE-2026-130983, CVE-2026-130984, CVE-2026-130985, CVE-2026-130986, CVE-2026-130987, CVE-2026-130988, CVE-2026-130989, CVE-2026-130990, CVE-2026-130991, CVE-2026-130992, CVE-2026-130993, CVE-2026-130994, CVE-2026-130995, CVE-2026-130996, CVE-2026-130997, CVE-2026-130998, CVE-2026-130999, CVE-2026-131000, CVE-2026-131001, CVE-2026-131002, CVE-2026-131003, CVE-2026-131004, CVE-2026-131005, CVE-2026-131006, CVE-2026-131007, CVE-2026-131008, CVE-2026-131009, CVE-2026-131010, CVE-2026-131011, CVE-2026-131012, CVE-2026-131013, CVE-2026-131014, CVE-2026-131015, CVE-2026-131016, CVE-2026-131017, CVE-2026-131018, CVE-2026-131019, CVE-2026-131020, CVE-2026-131021, CVE-2026-131022, CVE-2026-131023, CVE-2026-131024, CVE-2026-131025, CVE-2026-131026, CVE-2026-131027, CVE-2026-131028, CVE-2026-131029, CVE-2026-131030, CVE-2026-131031, CVE-2026-131032, CVE-2026-131033, CVE-2026-131034, CVE-2026-131035, CVE-2026-131036, CVE-2026-131037, CVE-2026-131038, CVE-2026-131039, CVE-2026-131040, CVE-2026-131041, CVE-2026-131042, CVE-2026-131043, CVE-2026-131044, CVE-2026-131045, CVE-2026-131046, CVE-2026-131047, CVE-2026-131048, CVE-2026-131049, CVE-2026-131050, CVE-2026-131051, CVE-2026-131052, CVE-2026-131053, CVE-2026-131054, CVE-2026-131055, CVE-2026-131056, CVE-2026-131057, CVE-2026-131058, CVE-2026-131059, CVE-2026-131060, CVE-2026-131061, CVE-2026-131062, CVE-2026-131063, CVE-2026-131064, CVE-2026-131065, CVE-2026-131066, CVE-2026-131067, CVE-2026-131068, CVE-2026-131069, CVE-2026-131070, CVE-2026-131071, CVE-2026-131072, CVE-2026-131073, CVE-2026-131074, CVE-2026-131075, CVE-2026-131076, CVE-2026-131077, CVE-2026-131078, CVE-2026-131079, CVE-2026-131080, CVE-2026-131081, CVE-2026-131082, CVE-2026-131083, CVE-2026-131084, CVE-2026-131085, CVE-2026-131086, CVE-2026-131087, CVE-2026-131088, CVE-2026-131089, CVE-2026-131090, CVE-2026-131091, CVE-2026-131092, CVE-2026-131093, CVE-2026-131094, CVE-2026-131095, CVE-2026-131096, CVE-2026-131097, CVE-2026-131098, CVE-2026-131099, CVE-2026-131100, CVE-2026-131101, CVE-2026-131102, CVE-2026-131103, CVE-2026-131104, CVE-2026-131105, CVE-2026-131106
Authoritative release date2026-11-17T19:12:07Z — Google Atom feed desktop publication; Android was published at 19:57:34 UTC.
Authority revision dateGoogle’s feed records an update at 2026-11-17T20:48:16.555Z; a separate material revision is not established.
Affected versionsDesktop and Android deployments that have not received the cited Chrome 158 Stable update require review. Google does not state a complete per-CVE affected-version range in these release posts.
Fixed versionWindows/macOS: 158.0.8127.36 or 158.0.8127.37; Linux: 158.0.8127.36; Android: 158.0.8127.42, or supported later fixed releases
CVSS base scoreNot provided by the authority
CVSS severityCritical
Exploitation statusThe cited authorities do not confirm exploitation of these vulnerabilities in the wild.; no exploitation claim is inferred.

What Changed

Google promoted Chrome 158 to Stable with 204 security fixes, including issues it rates Critical. The Android announcement explicitly carries the corresponding desktop security fixes unless stated otherwise.

What To Validate Now

  1. Inventory. Identify installed and running browser versions, update policies, rollout holds and platform owners.
  2. Establish applicability. Match the Stable channel and platform. Extended Stable and ChromeOS have separate announcements; do not apply these build numbers to them.
  3. Remediate. Use supported Chrome update channels and managed deployment tooling. Confirm Android availability through Google Play and resolve policy blocks that prevent the approved update.
  4. Validate. Verify the running build after restart and exercise enterprise authentication, extensions, media and graphics workflows. Retain inventory, deployment and exception evidence.
  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

Critical is Google’s highest listed severity, not an inferred CVSS score. Rollout is phased and some bug details remain restricted; neither establishes exploitation. Maintain a tested recovery plan without silently reverting to a vulnerable build.

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.