Google has moved Chrome 156 to the stable desktop channel with 353 security fixes, including six critical vulnerabilities affecting components such as CSS, Accessibility, Skia and WebRTC.
The official Chrome release notice says the update is rolling out to Windows, macOS and Linux “over the coming days/weeks.” The corrected builds are:
- Windows and macOS: 156.0.8078.47/.48
- Linux: 156.0.8078.47
The covered changelog runs from 155.0.8059.85 to 156.0.8078.47. Users and administrators should verify that installations have reached one of the fixed builds, particularly on managed systems where Google’s staged rollout may delay availability.
Memory-safety defects dominate the update
According to SecurityWeek’s analysis, the 353 fixes comprise six critical, 61 high-severity, 197 medium-severity and 89 low-severity issues.
The same analysis counted:
- 163 memory-corruption bugs
- 125 use-after-free vulnerabilities
- 17 out-of-bounds reads
- 36 improper-input-validation issues
Those categories account for 341 of the 353 fixes. The cited breakdown does not classify the remaining 12.
Memory corruption and use-after-free flaws arise when software mishandles memory boundaries or continues using memory after it has been released. Depending on the affected component and available mitigations, attackers may be able to read data, crash the browser or execute code. The NVD descriptions for the most serious Chrome 156 issues generally involve a victim opening a crafted HTML page.
Six critical vulnerabilities span core browser components
Google classified five of the critical issues as memory corruption and one as use after free. The “reported” dates below indicate when Google received each report, not when a patch was published or publicly disclosed.
| Vulnerability | Component and class | Potential effect described by NVD | CVSS | Reporter listed by Google | Reported |
|---|---|---|---|---|---|
| CVE-2026-113341 | Skia memory corruption | Potential memory disclosure inside the sandbox through crafted HTML; the NVD description specifically scopes this issue to Chrome on Android before 156.0.8078.47 | 6.5 | 2026-10-03 | |
| CVE-2026-113279 | Accessibility memory corruption | Potential arbitrary code execution inside the sandbox | 8.8 | Xinyang Ge | 2026-10-05 |
| CVE-2026-113072 | CSS memory corruption | Potential arbitrary code execution outside the sandbox | 9.6 | Xinyang Ge | 2026-10-06 |
| CVE-2026-113280 | Paint memory corruption | Arbitrary code execution inside the sandbox | 8.8 | Xinyang Ge | 2026-10-06 |
| CVE-2026-113271 | Accessibility use after free | Arbitrary code execution inside the sandbox | 8.8 | Xinyang Ge (Anthropic), assisted by Claude | 2026-10-08 |
| CVE-2026-113303 | WebRTC memory corruption | Potential arbitrary code execution inside the sandbox | 8.8 | OpenAI Codex Security (kylebot) | 2026-10-15 |
CVE-2026-113072 stands out because its NVD description says crafted HTML could potentially lead to code execution outside Chrome’s sandbox. It carries a CVSS 3.1 score of 9.6, with network access, low attack complexity and user interaction required.
The different CVSS scores and Chromium severity labels reflect separate rating systems. For example, Google classifies CVE-2026-113341 as critical, while its NVD vector gives it a score of 6.5 because the described effect is limited to reading memory inside the sandbox.
Site Isolation flaw earns the largest disclosed reward
Among the high-severity bugs, CVE-2026-113101 received the largest disclosed bounty: $10,000 for Quyen Son of VinFast.
This use-after-free vulnerability affects Site Isolation in Chrome versions before 156.0.8078.47. According to its NVD description, a remote attacker could use a crafted HTML page to execute arbitrary code inside the sandbox. It has a CVSS score of 8.8 and is classified as CWE-416.
Another high-severity issue, CVE-2026-113097, is a use-after-free defect in FileSystem. Its NVD entry also describes potential code execution inside the sandbox through crafted HTML and assigns a CVSS score of 8.8.
Google reported paying $50,000 in total for 24 vulnerabilities. Reward amounts for another 44 issues were not disclosed. SecurityWeek’s tally says 285 vulnerabilities received no reward, including 266 credited to Google and others attributed to Xinyang Ge or OpenAI Codex Security.
Google’s credits identify some findings as assisted by Anthropic’s Claude or submitted under OpenAI Codex Security. Those attributions describe how Google listed the reporters; they do not by themselves establish how much of the discovery or analysis was performed autonomously by an AI system.
Exploit details remain restricted during rollout
Google said bug links and technical details may remain unavailable until most users have installed the update. Restrictions may last longer when a vulnerability affects a third-party library used by other projects that have not yet shipped their own fixes.
SecurityWeek reported that Google’s announcement did not mention any of the 353 vulnerabilities being exploited in the wild. That absence should not be read as confirmation that exploitation has been ruled out.
For desktop users and enterprise administrators, the concrete defensive step is to confirm deployment of Chrome 156.0.8078.47/.48 on Windows and macOS or 156.0.8078.47 on Linux. Older builds remain within the affected range addressed by this security release.
