Chrome 158 Ships Two Critical Memory-Safety Fixes, Both Credited to AI-Assisted Research
Key Facts
- The desktop update brings Chrome to 158.0.8127.36/.37 on Windows and Mac, and 158.0.8127.36 on Linux.
- CVE-2026-131008 is a Critical use after free in GarbageCollection, reported by Xinyang Ge (Anthropic) on 2026-10-13 and assisted by Claude, under issue 574686297.
- CVE-2026-131060 is a Critical buffer overflow in Media, reported by Xinyang Ge (Anthropic) on 2026-10-07 and assisted by Claude, under issue 573128234.
- CVE-2026-130910 is a High-severity protection mechanism failure in ANGLE, reported by Xinyang Ge (Anthropic) on 2026-10-26 with a $4,000 bounty under issue 576579698.
- CVE-2026-130970 is a High-severity uninitialized resource in GPU, reported by Google on 2026-10-02 under issue 568937157.
Google has published a Stable channel update for Chrome on Windows, Mac and Linux. On Windows and Mac the browser moves to 158.0.8127.36/.37. On Linux it moves to 158.0.8127.36.
A version string is the least interesting thing in a security release, and the most useful. It is the part you can check without trusting anyone. Everything else in an advisory, the severity ratings, the reporter names, the issue numbers, is a record of work already finished.
The desktop release lists four entries rated High or above. Two are Critical. Two are High. The count is small, and each entry is short enough to read in full. Taken together they describe a patch in which the interesting part is not the bug classes, which are old and familiar, but the paperwork around them: who found what, when they filed it, and what the advisory does not say.
Two Critical bugs, one reporter, one assistant
Both Critical entries name Xinyang Ge of Anthropic as the reporter, and both list Claude as an assistant.
CVE-2026-131008 is a use after free in GarbageCollection. Ge filed it on 2026-10-13, under issue 574686297.
CVE-2026-131060 is a buffer overflow in Media. Ge filed it on 2026-10-07, under issue 573128234. It is the older of the two by six days.
Neither entry carries a bounty figure. The advisory marks that field N/A for both. A reader who wants to know whether money changed hands will not learn it here.
Use after free and buffer overflow are the two most heavily studied memory-safety failures in software, and the two classes that fuzzing and static analysis have been aimed at for years. That a pair of them should turn up in GarbageCollection and Media, code that sits close to untrusted input, is not surprising. That both arrived through the same reporter, in the same month, with an AI assistant named in the credit, is the part worth noticing.
The filing dates are six days apart. Between a bug report and a shipped fix, a vendor reproduces the problem, writes the patch, and tests it against the rest of the engine. Two Critical memory-safety fixes in six days is a normal pace for a large team. It is a fast one for a single reporter.
ANGLE and the GPU
CVE-2026-130910 is a protection mechanism failure in ANGLE. Ge reported it on 2026-10-26 under issue 576579698, and the advisory records a $4,000 bounty. That is the only dollar figure in the set, and it is attached to the one bug Ge filed without an assistant.
CVE-2026-130970 is an uninitialized resource in GPU. Google reported it on 2026-10-02, under issue 568937157, with the bounty field marked N/A. Self-reported bugs rarely make news on their own. They are still useful as a signal: when a vendor files against its own GPU code, internal review has reached the path that matters.
ANGLE is the layer Chrome uses to run graphics code across different GPU drivers, and the graphics stack is where a memory bug is hardest to reproduce and most expensive when it lands. Two High-severity findings in that neighbourhood, filed three weeks apart, are a reminder that the area remains live.
The disclosure ledger
Read the four entries as a ledger and a shape appears. Every filing falls between 2026-10-02 and 2026-10-26. The two Critical bugs came first, in the first half of October. The paid ANGLE finding came last. The self-reported GPU bug is the earliest of all.
The bounties are almost entirely absent. Three of the four entries read N/A. Only CVE-2026-130910 carries a sum, and $4,000 is modest against the usual range for a Critical memory-safety flaw in a browser. Whatever the reasons, the public record shows no large payout for the two most serious findings in this release.
What the record does show, plainly, is an AI assistant credited on two Critical bugs in a shipping browser. That is now an ordinary line in a vendor advisory rather than a novelty.
Applying the update
The fix is a version number. On Windows and Mac, check for 158.0.8127.36/.37. On Linux, check for 158.0.8127.36. If the browser reports anything older, the update has not landed.
There is nothing exotic in the advice. The bugs are memory-safety failures in components that handle outside input, and the patch closes them. The reason to install it promptly is not that these particular flaws are known to be exploited, a question the record above does not answer, but that a use after free and a buffer overflow in a browser age badly once the fix ships and the description does not.
Sources & References
- Chrome Releases: Stable Channel Update for Desktop. Primary vendor advisory. https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop_01699533288.html
- Source referenced in coverage https://www.malwarebytes.com/blog/bugs/2026/11/chrome-patches-six-critical-flaws-two-found-with-ais-help
- CVE-2026-131031 — NIST National Vulnerability Database entry. https://nvd.nist.gov/vuln/detail/CVE-2026-131031
- CVE-2026-130963 — NIST National Vulnerability Database entry. https://nvd.nist.gov/vuln/detail/CVE-2026-130963
- CVE-2026-131031 — National Vulnerability Database
- CVE-2026-130963 — National Vulnerability Database
- CVE-2026-131060 — National Vulnerability Database
- CVE-2026-131008 — National Vulnerability Database
- CVE-2026-131054 — National Vulnerability Database
- CVE-2026-130975 — National Vulnerability Database
- CVE-2026-130910 — National Vulnerability Database
- CVE-2026-130943 — National Vulnerability Database
- CVE-2026-130994 — National Vulnerability Database
- CVE-2026-130909 — National Vulnerability Database
- CVE-2026-131065 — National Vulnerability Database
- CVE-2026-131100 — National Vulnerability Database
- CVE-2026-130979 — National Vulnerability Database
- CVE-2026-131079 — National Vulnerability Database
- CVE-2026-130940 — National Vulnerability Database
- CVE-2026-130954 — National Vulnerability Database
- CVE-2026-130996 — National Vulnerability Database
- CVE-2026-130970 — National Vulnerability Database
- CVE-2026-131057 — National Vulnerability Database
- CVE-2026-130945 — National Vulnerability Database
- CVE-2026-131084 — National Vulnerability Database
- CVE-2026-131090 — National Vulnerability Database
- CVE-2026-130982 — National Vulnerability Database
- CVE-2026-131021 — National Vulnerability Database
- CVE-2026-131022 — National Vulnerability Database
- CVE-2026-131081 — National Vulnerability Database
- CVE-2026-130961 — National Vulnerability Database
- CVE-2026-130984 — National Vulnerability Database
- CVE-2026-130946 — National Vulnerability Database
- CVE-2026-131045 — National Vulnerability Database
- CVE-2026-131042 — National Vulnerability Database
- CVE-2026-131059 — National Vulnerability Database
- CVE-2026-130934 — National Vulnerability Database
- CVE-2026-130951 — National Vulnerability Database
- CVE-2026-131013 — National Vulnerability Database
- CVE-2026-130941 — National Vulnerability Database
- CVE-2026-131068 — National Vulnerability Database
SecurityXP delivers cybersecurity news, vulnerability analysis, data breach reports, and threat intelligence.
Security Digest
The most important cybersecurity stories, CVE alerts, and threat intelligence — one concise email. Unsubscribe anytime.
Related Articles
SAP fixes critical flaws in NetWeaver and Commerce Cloud
Uncovering Critical Flaws in SAP NetWeaver and Commerce Cloud SAP's June 2026 Security Patch package is a big deal. It fixes 15 vulnerabilities, including...
NGINX2Root: Five Critical NGINX RCE Flaws and the Limits of the Public Exploit Record
On November 18, F5 released an out-of-band security update covering 10 vulnerabilities in NGINX Plus and NGINX Open Source.
Critical Gitea Flaw Under Active Exploitation, Researchers Warn Vulnerability (CVE-2026-20896)
Specific to Gitea’s official Docker images, the critical-severity security defect is tracked as CVE-2026-20896 (CVSS score of 9.8) and can be exploited with...
Critical Adobe ColdFusion Vulnerability Exploited in Attacks (CVE-2026-48282)
However, according to the vulnerability intelligence platform KEVIntel, hackers began exploiting CVE-2026-48282 within two hours of its public disclosure...