# Chrome 158 fixes six critical memory safety flaws on desktop

Canonical: https://www.oktsec.com/radar/google-chrome-158-desktop-security-update
Publisher: Oktsec
Language: en
Published: 2026-11-18T21:03:37Z
Updated: 2026-11-18T21:03:37Z
Record reviewed: 2026-11-18T21:03:37Z
Latest evidence check: 2026-11-18T21:03:37Z
Disclosed: 2026-11-17

Google shipped 204 security fixes in the November 17 desktop Stable update. Six rated critical affect WebView, GPU, media, garbage collection, ANGLE and WebAudio.

## Evidence and response priority

- Category: Vulnerability
- Oktsec priority: Review this week
- Rationale: Google rates six fixes critical and provides an updated Stable build for each desktop operating system.
- Evidence: Attacks not established
- Verification: Vendor confirmed
- Fix status: Fix available
- Exposure requirement: Application or configuration dependent
- Vendor: Google
- Products: Google Chrome desktop Stable
- CVEs: CVE-2026-130963, CVE-2026-131031, CVE-2026-131060, CVE-2026-131008, CVE-2026-131054, CVE-2026-130975

## Technical overview

Google is rolling out Chrome 158 over several days or weeks. The six critical CVEs are a subset of the release. Google’s November 17 bulletin does not report exploitation of those six flaws. The earlier exploitation notice for Chrome 157 concerned a different CVE.

## Recommended response

Apply the desktop Stable update, relaunch the browser and check the running build. Verify browser automation hosts separately.

Relevant to: Check the active update channel and build on managed desktop browsers.

## CVE attribution

- CVE-2026-130963: Google — Google Chrome desktop Stable. [Source](https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop_01699533288.html)
- CVE-2026-131031: Google — Google Chrome desktop Stable. [Source](https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop_01699533288.html)
- CVE-2026-131060: Google — Google Chrome desktop Stable. [Source](https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop_01699533288.html)
- CVE-2026-131008: Google — Google Chrome desktop Stable. [Source](https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop_01699533288.html)
- CVE-2026-131054: Google — Google Chrome desktop Stable. [Source](https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop_01699533288.html)
- CVE-2026-130975: Google — Google Chrome desktop Stable. [Source](https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop_01699533288.html)

## Affected systems and fixes

### Linux Stable

Affected: Desktop Stable installations before the November 17 release.

Fixed release / action: 158.0.8127.36

### Windows and macOS Stable

Affected: Desktop Stable installations before the November 17 release.

Fixed release / action: 158.0.8127.36 or 158.0.8127.37

Confirm the running version against the vendor advisory, including any distribution backports.

## CISA KEV evidence

Catalog: 2026.11.18
Checked: 2026-11-18T21:06:31.057Z

No matching CVE appears in the reviewed catalog snapshot.

CISA KEV inclusion establishes known exploitation of the listed CVE, not compromise of your environment. Absence does not rule out exploitation. The date added is not the first attack date. Federal deadlines and forensic triage requirements are context, not universal obligations for private organizations or businesses in Latin America.

## Supporting evidence

Snapshot checked: 2026-11-19T21:12:22.272Z. These dates do not change the incident’s editorial review date.

### FIRST EPSS forecast

- [CVE-2026-131060](https://api.first.org/data/v1/epss?cve=CVE-2026-131060): 0.44% probability of observed exploitation in the next 30 days; percentile 38.75%; score date 2026-11-19.
- [CVE-2026-131054](https://api.first.org/data/v1/epss?cve=CVE-2026-131054): 0.43% probability of observed exploitation in the next 30 days; percentile 37.73%; score date 2026-11-19.
- [CVE-2026-131031](https://api.first.org/data/v1/epss?cve=CVE-2026-131031): 0.43% probability of observed exploitation in the next 30 days; percentile 37.77%; score date 2026-11-19.
- [CVE-2026-131008](https://api.first.org/data/v1/epss?cve=CVE-2026-131008): 0.4% probability of observed exploitation in the next 30 days; percentile 34.6%; score date 2026-11-19.
- [CVE-2026-130975](https://api.first.org/data/v1/epss?cve=CVE-2026-130975): 0.5% probability of observed exploitation in the next 30 days; percentile 43.69%; score date 2026-11-19.
- [CVE-2026-130963](https://api.first.org/data/v1/epss?cve=CVE-2026-130963): 0.43% probability of observed exploitation in the next 30 days; percentile 37.82%; score date 2026-11-19.

EPSS is a prediction, not exploitation evidence or organization-specific risk. Confirmed exploitation takes precedence. A missing score is not zero. Check status: available; last successful check: 2026-11-19T21:12:22.272Z.

## Response checklist

1. **Find Stable installations** — Check the active update channel and build on managed desktop browsers.
2. **Relaunch and verify** — Relaunch updated browsers and check the running build on each operating system.
3. **Inspect automated browsers** — Check the executable used by unattended jobs. Automation may use a different browser installation from the interactive desktop.

## Relevance to AI environments

Check the executable used by unattended jobs. Automation may use a different browser installation from the interactive desktop.

## Sources

- [November 17 desktop Stable release and security fixes](https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop_01699533288.html) — Google; Vendor notice; checked 2026-11-18T21:03:37Z

## Editorial record

- 2026-11-18T21:03:37Z: Added the November 17 desktop Stable release and six critical fixes identified by Google.

## Related incidents

- [Chrome 157: 83 more security fixes; update and relaunch](https://www.oktsec.com/radar/google-chrome-157-security-update)

## Use this advisory in Radar

Use the Advisory view to understand the issue and its evidence, Affected systems to compare versions, and Response plan to record applicability, an owner and action progress. Plans are saved only in the current browser and can be downloaded for sharing; they are not a shared team account or an automated scan. Completing a plan does not validate remediation. Talk to Oktsec opens a technical consultation with the advisory and selected service preserved. Scope, fees and access are agreed before any assessment.

[Open advisory](https://www.oktsec.com/radar/google-chrome-158-desktop-security-update) · [Build a response plan](https://www.oktsec.com/radar/google-chrome-158-desktop-security-update#review-workspace)

- [Exposure check consultation](https://www.oktsec.com/contact?source=radar&intent=assessment&item=google-chrome-158-desktop-security-update&service=exposure_check)
- [Patch verification consultation](https://www.oktsec.com/contact?source=radar&intent=assessment&item=google-chrome-158-desktop-security-update&service=patch_verification)

## Scope and corrections

Radar is a selected editorial collection, not a complete vulnerability database or a scan of your environment. Priorities are Oktsec analysis. Source confirmation and checklist completion do not establish whether your systems are compromised or secure.

[Sources and methodology](https://www.oktsec.com/radar/about). Report corrections with supporting sources to info@oktsec.com. Do not send secrets or private incident data.

