EN PT-BR
← Voltar ao feed
high

Google Chrome 157 fixes 213 vulnerabilities, including seven critical memory-safety flaws in Dawn, ANGLE and WebGL

3 fonte(s) · 2 atualização(ões) · 1 repetição(ões) · publicado 03/11/2026 20:21 · coletado há 16 horas

Matéria consolidada. Reúne 2 matérias que o Tifon tinha publicado separadamente sobre a mesma história. A IA reescreveu o relatório com o que as 3 fontes trouxeram em 05/11/2026 00:08; os links antigos trazem para cá.

Fontes: malwarebytes.com ↗ securityweek.com ↗ securityonline.info ↗

Google released Chrome 157 (157.0.8103.38/.39) to the stable channel, fixing 213 security issues, an unusually large batch for one release. Seven are rated critical memory-safety bugs: buffer overflows in Dawn (WebGPU), memory corruption in ANGLE and four use-after-free defects (securityonline.info, securityweek.com). Google has not reported in-the-wild exploitation of any of the fixes (securityweek.com, securityonline.info). Critical browser bugs of this kind could let a malicious web page escape the sandbox and execute arbitrary code (securityonline.info). AI-assisted research played a large part: Anthropic (Xinyang Ge, aided by Claude) and OpenAI Codex Security were credited for 17 of the bugs combined (securityonline.info). Users should update promptly.

Entenda a falha

A vulnerabilidade

Chrome 157 fixes 213 security issues, seven of them critical memory-safety bugs. The most severe is CVE-2026-121156 (CVSS 9.6), a buffer overflow in Dawn, Chrome's WebGPU engine. CVE-2026-121247 is a second Dawn overflow. CVE-2026-121229 is memory corruption in ANGLE; Malwarebytes says it affects Chrome for Android and could let a remote attacker run code outside the sandbox through a crafted HTML page. CVE-2026-121246 (WebGL), CVE-2026-121035 (Prerender), CVE-2026-121203 (Geometry) and CVE-2026-121126 (Core) are use-after-free bugs. The attacker needs the victim to open a malicious page. Fixed in 157.0.8103.38 (Linux, Android) and 157.0.8103.38/.39 (Windows, Mac), and in 156.0.8078.88 for Extended Stable. Google reports no exploitation in the wild.

Como funciona

A web page sends content that Chrome handles in graphics and rendering components. Dawn checks WebGPU instructions and translates them into commands for the device's graphics system. ANGLE is the graphics translation layer. Prerender loads, renders and runs the JavaScript of a page in the background before the user navigates to it. In the use-after-free cases, the code releases a block of memory but keeps using it afterwards. In the overflow cases, it writes more data than a buffer can hold. In both, memory the program trusts can end up holding attacker-influenced data, which could let the attacker hijack execution. Google keeps per-bug details private until most users have updated.

Por que é vulnerável

The root causes are memory-safety errors in native browser code. Some components free memory while references to it are still in use (use-after-free). Dawn writes beyond the bounds of a buffer (buffer overflow), and ANGLE has memory corruption that the articles do not describe further. The articles do not explain why these bugs went unnoticed or what each patch changes beyond shipping in Chrome 157.

Como foi descoberta

Google's internal teams reported 38 of the 84 critical and high-severity bugs. AI-assisted research played a large role: Anthropic researchers, assisted by Claude, reported 12 bugs and OpenAI Codex Security found five more. Xinyang Ge of Anthropic, working with Claude, found the Prerender flaw CVE-2026-121035. Of the critical bugs without a listed reward, Google reported two, Ge two and researcher Wenbin Liu one. The top rewards of $10,000 went to the Dawn overflow and a BackgroundFetch authorization bug, and the ANGLE bug earned $1,000. Google paid $31,000 in total and had not set the reward for 39 flaws. The fixes came in the stable channel update of November 3.

Explicação gerada por IA a partir da matéria e dos artigos, em 05/11/2026 00:23.

Detalhes técnicos

  • CVE-2026-121156 (CVSS 9.6) and CVE-2026-121247: buffer overflows in Dawn (WebGPU) (securityonline.info).
  • CVE-2026-121229: memory corruption in ANGLE (securityonline.info).
  • CVE-2026-121246: use-after-free in WebGL (securityonline.info).
  • CVE-2026-121035: use-after-free in Prerender, found by Xinyang Ge of Anthropic with Claude (securityonline.info).
  • CVE-2026-121203: use-after-free in Geometry (securityonline.info).
  • CVE-2026-121126: use-after-free in Core (securityonline.info).
  • Besides the seven critical flaws, 77 are high severity (securityweek.com). V8 has 10 high-severity type confusion flaws, and other fixes affect PDFium, Skia, Media and FileSystem (securityonline.info).
  • Bug classes (securityweek.com): incorrect/missing authorization (51), use-after-free (45), UI misrepresentation (19), type confusion (13), information leak (13), out-of-bounds read/write (11), improper input validation (9), uninitialized resource (9).
  • Google's internal teams found 38 of the 84 critical/high bugs (securityonline.info), including several of the critical flaws (securityweek.com). Other credited reporters include Wenbin Liu (securityweek.com).
  • Bug bounty: $31,000 paid so far, with payouts for 39 flaws still undetermined (securityweek.com). Top rewards of $10,000 went to the Dawn overflow and a BackgroundFetch authorization issue (securityonline.info).

Remediação

Update to Chrome 157.0.8103.38 on Linux or 157.0.8103.38/.39 on Windows and macOS via Settings > About Chrome, then restart the browser (securityonline.info, securityweek.com). Extended Stable users should update to 156.0.8078.88 on Windows and Mac (securityonline.info). The rollout is gradual over the coming days or weeks (securityonline.info).

Relatos divergentes

  • Use-after-free count: securityonline.info reports 35 use-after-free issues, while securityweek.com reports 45. The sources do not explain the difference, and securityweek.com is the more recent. Neither figure is vendor-confirmed in the input.

Linha do tempo

  1. securityweek.com ↗ · pub. 04/11/2026 07:38 · coletado 04/11 09:00

    Chrome 157 Patches 213 Vulnerabilities, Seven Critical Memory Safety Flaws

    ler a análise desta fonte

    Google released Chrome 157 to the stable channel, fixing 213 vulnerabilities including seven critical memory safety bugs. The most severe issues involve a buffer overflow in Dawn (the WebGPU implementation) and a memory corruption flaw in ANGLE, alongside four use-after-free defects and another buffer overflow. Google paid out $31,000 in bug bounty rewards so far, with payouts for 39 flaws still undetermined. No in-the-wild exploitation has been observed for any of the patched issues, but users are urged to update promptly given the volume and severity of fixes.

    Technical Details

    The update addresses 77 high-severity vulnerabilities in addition to the seven critical ones. Common bug classes include incorrect/missing authorization (51), use-after-free (45), UI misrepresentation (19), type confusion (13), information leak (13), out-of-bounds read/write (11), improper input validation (9), and uninitialized resource (9). Reporters credited include Anthropic's Xinyang Ge and researcher Wenbin Liu, among others; Google itself discovered several of the critical flaws.

    Remediation

    Chrome 157 is rolling out as versions 157.0.8103.38/.39 for Windows and macOS, and 157.0.8103.38 for Linux. Users should update their browsers as soon as the new version becomes available.

  2. securityonline.info ↗ · pub. 03/11/2026 20:21 · coletado 04/11 08:52 primeiro registro

    Chrome 157 Patches 213 Flaws, Including 7 Critical Memory Corruption Bugs

    ler a análise desta fonte

    Google has released Chrome 157 (157.0.8103.38/.39) to the stable channel, fixing 213 security issues, an unusually large batch for a single release. Seven flaws are rated critical, including buffer overflows in the Dawn WebGPU engine and memory corruption in ANGLE, along with multiple use-after-free bugs in WebGL, Prerender, Geometry and Core. Google has not confirmed exploitation in the wild for any of these issues, but critical browser bugs could allow a malicious web page to escape sandboxing and execute arbitrary code. AI-assisted research played a significant role this cycle, with Anthropic (aided by Claude) and OpenAI Codex Security credited for 17 of the reported bugs combined.

    Technical Details

    • CVE-2026-121156 (CVSS 9.6) and CVE-2026-121247: buffer overflows in Dawn (WebGPU)
    • CVE-2026-121229: memory corruption in ANGLE
    • CVE-2026-121246: use-after-free in WebGL
    • CVE-2026-121035: use-after-free in Prerender (found by Xinyang Ge of Anthropic with Claude)
    • CVE-2026-121203: use-after-free in Geometry
    • CVE-2026-121126: use-after-free in Core
    • Use-after-free bugs account for 35 of the listed issues; V8 has 10 high-severity type confusion flaws; other fixes affect PDFium, Skia, Media and FileSystem.
    • Google's internal teams found 38 of the 84 critical/high severity bugs; top bug bounty rewards were $10,000 for the Dawn overflow and a BackgroundFetch authorization issue.

    Remediation

    Update to Chrome 157.0.8103.38 (Linux) or 157.0.8103.38/.39 (Windows/Mac) via Settings > About Chrome, then restart the browser. Extended Stable channel users should update to 156.0.8078.88 on Windows and Mac. The rollout occurs gradually over coming days/weeks.

Repetiram sem novidade