Skip to main content
ISO/IEC 27001:2022 · Cert #2967/NET27A

Chrome 158 fixes ANGLE out of bounds read CVE-2026-131057 (CVSS 9.6)

Chrome 158 fixes CVE-2026-131057, out of bounds read in ANGLE (CVSS 9.6 from CISA-ADP; Chromium severity High). Fixed in 158.0.8127.36/.37 for Windows, Mac and Linux.

Security advisory card: Chrome 158 fixes ANGLE out of bounds read CVE-2026-131057 (CVSS 9.6). Severity Critical, CVSS 9.6. CVE-2026-131057.

Advisory at a glance

CVE
CVE-2026-131057
Severity
Severity: Critical CVSS v3.1 9.6
Attack vector
Network
Privileges required: none
Exploitation evidence
Not listed in the CISA KEV catalog (record checked Nov 21, 2026)
Absence from KEV is not proof that a flaw is not exploited.
Last reviewed

Google released Chrome 158 to the stable channel for Windows, Mac and Linux on 17 November 2026. The update includes 204 security fixes. One of them is CVE-2026-131057, an out of bounds read in the Chrome component ANGLE. NVD lists a CVSS 3.1 base score of 9.6 (Critical), supplied by CISA-ADP. Google's own Chromium severity rating is lower: High. The fixed version is Chrome 158.0.8127.36 for Linux and 158.0.8127.36/.37 for Windows and Mac.

Advisory details

FieldValue (as published by Google)
Release noteStable Channel Update for Desktop
PublishedTuesday, November 17, 2026
ReleaseChrome 158 promoted to the stable channel for Windows, Mac and Linux
CVE IDCVE-2026-131057
IssueOut of bounds read in ANGLE
Chromium severityHigh
Chromium bug ID569191970
RewardN/A
Reported byGoogle on 2026-10-03
Security fixes in this release204
Rollout"This will roll out over the coming days/weeks."

Affected and fixed versions

PlatformAffectedFixed version
LinuxGoogle Chrome prior to 158.0.8127.36158.0.8127.36
WindowsGoogle Chrome prior to 158.0.8127.36158.0.8127.36/.37
MacGoogle Chrome prior to 158.0.8127.36158.0.8127.36/.37

Google notes that access to bug details may stay restricted until a majority of users are updated with a fix.

What NVD says

NVD's description, quoted in full:

Out of bounds read in ANGLE in Google Chrome on on Android prior to 158.0.8127.36 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)

Exploitation status

CVE-2026-131057 is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Google's release note does not report attacks using it. It is not known to be exploited.

Terms explained

  • ANGLE: the graphics layer Chromium uses to translate OpenGL ES and WebGL calls into the graphics interface of the operating system.
  • Out of bounds read / CWE-125: CWE-125 is the MITRE Common Weakness Enumeration entry "Out-of-bounds Read". The program reads data outside the memory buffer it is meant to use.
  • Sandbox: Chrome runs web content in a restricted process. Code that runs "outside the sandbox" is no longer held by those restrictions.
  • CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H: AV:N means the attack works over the network. AC:L means low attack complexity. PR:N means no privileges are needed. UI:R means a user must take an action, such as opening a crafted HTML page. S:C means the impact reaches beyond the vulnerable component. C:H, I:H and A:H mean high impact on confidentiality, integrity and availability.
  • Chromium security severity: Google's own rating of a Chrome bug (Critical, High, Medium or Low). It is separate from the CVSS score in NVD.

What This Means for IT Teams

Any Windows, Mac or Linux computer running Google Chrome below version 158.0.8127.36 is in scope. NVD's description refers to Chrome on Android, while Google lists the fix in its desktop release; desktop and Android installs below 158.0.8127.36 are both worth checking. A successful attack needs a user to open a crafted HTML page; no privileges are needed.

Compare the installed Chrome version with 158.0.8127.36 (Linux) or 158.0.8127.36/.37 (Windows and Mac) and deploy Chrome 158 where it is missing. Google rolls the update out over days or weeks, so managed fleets can deploy Chrome 158 through patch management instead of waiting for the rollout. Google lists no workaround.

The flaw is not in the CISA KEV catalog and is not known to be exploited.

NVD cross-check

  • Score source: NVD shows CVSS 3.1 vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, base score 9.6 (Critical), from CISA-ADP (NVD source ID 134c704f-9b21-4f2e-91b3-4a467353bcc0, which also supplies the "CISA Coordinator" SSVC entry) as a secondary score. NVD lists no CVSS 4.0 score and no primary NVD score.
  • Severity: Google rates the bug High; the CISA-ADP CVSS score is 9.6 (Critical). The two ratings use different scales.
  • Weakness: NVD lists CWE-125 (Out-of-bounds Read), supplied by Google.
  • Difference: the NVD description says "Google Chrome on on Android" (sic), and NVD's configuration pairs Chrome before 158.0.8127.36 with Android. Google lists the fix in its Stable Channel Update for Desktop, which covers Windows, Mac and Linux. The difference is noted here for checking.
  • Status: NVD published the record on 2026-11-17, last modified it on 2026-11-19 and marks it "Analyzed".

Another Chrome 158 fix is covered in Chrome 158 fixes ANGLE out of bounds write CVE-2026-130996 (CVSS 9.6).

Sources

  1. Stable Channel Update for Desktop (Chrome 158) (opens in a new tab) Google Chrome Releases Published Nov 17, 2026 Accessed Nov 21, 2026 chromereleases.googleblog.com
  2. NVD CVE API 2.0 record for CVE-2026-131057 (opens in a new tab) NIST National Vulnerability Database (NVD) Published Nov 17, 2026 Accessed Nov 21, 2026 services.nvd.nist.gov
  3. CISA Known Exploited Vulnerabilities catalog (JSON feed) (opens in a new tab) Cybersecurity and Infrastructure Security Agency (CISA) Published Nov 20, 2026 Accessed Nov 21, 2026 cisa.gov

How we research, review and correct articles: Editorial Standards, Ethics & Corrections Policy. Found an error? Tell us.

Networking Pulse · https://networkingpulse.com/news/security/google-chrome-158-angle-out-of-bounds-read-cve-2026-131057/

Cybersecurity & Compliance

Need help checking your exposure to this advisory?

Talk to our team about the devices and versions in your network and how to plan the update.