macOS · Application version · November 2, 2026

Google Chrome 157.0.8103.39

Google Chrome 157.0.8103.39, released November 2, 2026, fixes 196 CVEs in Google Chrome. None of them is reported as exploited. Patch Radar priority: Urgent. The latest Google Chrome is 157.0.8103.51, which also fixes every one of these CVEs.

Urgent

Superseded. The latest Google Chrome is 157.0.8103.51, which also fixes every CVE on this page. Install that instead.

CVEs closed

196

10 rated Critical

Exploited

None reported

Highest CVSS

9.6

Base score, 0 to 10

Highest EPSS

0.0048

41st percentile

Priority of the 196 CVEs

Patch now 0
                                Urgent 10
                                High 96
                                Routine 90

Applies to

Product	Version
Google Chrome	157.0.8103.39

CVEs this fix closes

Priority	CVE	Title	CVSS	EPSS	Exploitation
Urgent	CVE-2026-121156	Google Chrome: Buffer overflow	9.6	0.0048	None reported
Urgent	CVE-2026-121035	Chromium CVE-2026-121035: Use after free	9.6	0.0044	None reported
Urgent	CVE-2026-121126	Chromium CVE-2026-121126: Use after free	9.6	0.0041	None reported
Urgent	CVE-2026-121148	Google Chrome: Use after free	9.6	0.0041	None reported
Urgent	CVE-2026-121060	Google Chrome: Incorrect authorization	9.6	0.0041	None reported
Urgent	CVE-2026-121071	Google Chrome: Incorrect authorization	9.6	0.0040	None reported
Urgent	CVE-2026-121203	Chromium CVE-2026-121203: Use after free	8.8	0.0037	None reported
Urgent	CVE-2026-121076	Google Chrome: Use after free	9.6	0.0034	None reported
Urgent	CVE-2026-121077	Google Chrome: Use after free	9.6	0.0034	None reported
Urgent	CVE-2026-121073	Google Chrome: Use after free	9.6	0.0026	None reported
High	CVE-2026-121127	Chromium CVE-2026-121127: Use after free	8.8	0.0047	None reported
High	CVE-2026-121129	Chromium CVE-2026-121129: Use after free	8.8	0.0047	None reported
High	CVE-2026-121086	Chromium CVE-2026-121086: Buffer overflow	9.6	0.0045	None reported
High	CVE-2026-121249	Chromium CVE-2026-121249: Buffer overflow	9.6	0.0045	None reported
High	CVE-2026-121057	Google Chrome: Type confusion	8.8	0.0044	None reported
High	CVE-2026-121034	Chromium CVE-2026-121034: Use after free	9.6	0.0042	None reported
High	CVE-2026-121089	Chromium CVE-2026-121089: Use after free	9.6	0.0041	None reported
High	CVE-2026-121114	Chromium CVE-2026-121114: Use after free	9.6	0.0041	None reported
High	CVE-2026-121185	Chromium CVE-2026-121185: Use after free	9.6	0.0041	None reported
High	CVE-2026-121189	Chromium CVE-2026-121189: Use after free	9.6	0.0041	None reported
High	CVE-2026-121214	Chromium CVE-2026-121214: Use after free	9.6	0.0041	None reported
High	CVE-2026-121030	Chromium CVE-2026-121030: Incorrect authorization	9.6	0.0041	None reported
High	CVE-2026-121044	Google Chrome: Use after free	8.8	0.0041	None reported
High	CVE-2026-121052	Google Chrome: Use after free	8.8	0.0041	None reported
High	CVE-2026-121068	Google Chrome: Type confusion	8.8	0.0040	None reported

Other Google Chrome versions with security fixes

Google Chrome 156.0.8078.80
Google Chrome
Google Chrome 156.0.8078.74
Google Chrome
Google Chrome 156.0.8078.48
Google Chrome
Google Chrome 155.0.8059.85
Google Chrome
Google Chrome 155.0.8059.80
Google Chrome
Google Chrome 155.0.8059.40
Google Chrome

For tools and AI agents

This page as data: JSON · Markdown

Link to this page

If this page saved you time, a link to it in your ticket, advisory or write-up helps others find it.

HTML

<a href="https://patchblox.com/security/fix/macos/com.google.chrome-157.0.8103.39">Google Chrome 157.0.8103.39 on Patchblox Patch Radar</a>

Reusing the data? How to credit Patch Radar.

Is it current everywhere?

Patchblox finds every install below the fixed version, including per-user copies, and updates them from a signed catalog package.

Get a demo

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.