Windows apps · Application version · December 5, 2025

Google Chrome Dev (EXE) 145.0.7561.3

Google Chrome Dev (EXE) 145.0.7561.3, released December 5, 2025, fixes 14 CVEs in Google Chrome Dev (EXE). None of them is reported as exploited. Patch Radar priority: Urgent. The latest Google Chrome Dev (EXE) is 159.0.8144.0, which also fixes every one of these CVEs.

Urgent

Superseded. The latest Google Chrome Dev (EXE) is 159.0.8144.0, which also fixes every CVE on this page. Install that instead.

CVEs closed

4 rated Critical

Exploited

None reported

Highest CVSS

9.8

Base score, 0 to 10

Highest EPSS

0.0882

95th percentile

Priority of the 14 CVEs

Patch now 0
                                Urgent 4
                                High 6
                                Routine 4

Applies to

Product	Version
Google Chrome Dev (EXE)	145.0.7561.3

CVEs this fix closes

Priority	CVE	Title	CVSS	EPSS	Exploitation
Urgent	CVE-2026-0907	Chromium: CVE-2026-0907 Incorrect security UI in Split View	9.8	0.0882	None reported
Urgent	CVE-2026-0906	Chromium: CVE-2026-0906 Incorrect security UI	9.8	0.0036	None reported
Urgent	CVE-2026-0908	Chromium: CVE-2026-0908 Use after free in ANGLE	9.6	0.0032	None reported
Urgent	CVE-2026-0905	Chromium: CVE-2026-0905 Insufficient policy enforcement in Network	9.8	0.0025	None reported
High	CVE-2026-1862	Chromium: CVE-2026-1862 Type Confusion in V8	8.8	0.0064	None reported
High	CVE-2026-1861	Chromium: CVE-2026-1861 Heap buffer overflow in libvpx	8.8	0.0046	None reported
High	CVE-2026-0899	Chromium: CVE-2026-0899 Out of bounds memory access in V8	8.8	0.0041	None reported
High	CVE-2026-0900	Chromium: CVE-2026-0900 Inappropriate implementation in V8	8.8	0.0035	None reported
High	CVE-2026-0902	Chromium: CVE-2026-0902 Inappropriate implementation in V8	8.8	0.0030	None reported
High	CVE-2026-1220	Chromium: CVE-2026-1220 Race in V8	7.5	0.0030	None reported
Routine	CVE-2026-1504	Chromium: CVE-2026-1504 Inappropriate implementation in Background Fetch API	6.5	0.0026	None reported
Routine	CVE-2026-0901	Chromium: CVE-2026-0901 Inappropriate implementation in Blink	5.4	0.0022	None reported
Routine	CVE-2026-0903	Chromium: CVE-2026-0903 Insufficient validation of untrusted input in Downloads	5.4	0.0021	None reported
Routine	CVE-2026-0904	Chromium: CVE-2026-0904 Incorrect security UI in Digital Credentials	5.4	0.0019	None reported

Other Google Chrome Dev (EXE) versions with security fixes

Google Chrome Dev (EXE) 158.0.8106.0
Google Chrome Dev (EXE)
Google Chrome Dev (EXE) 157.0.8081.0
Google Chrome Dev (EXE)
Google Chrome Dev (EXE) 156.0.8063.3
Google Chrome Dev (EXE)
Google Chrome Dev (EXE) 155.0.8040.2
Google Chrome Dev (EXE)
Google Chrome Dev (EXE) 154.0.8013.2
Google Chrome Dev (EXE)
Google Chrome Dev (EXE) 153.0.7979.3
Google Chrome Dev (EXE)

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/windows-app/google.chrome.dev.exe-145.0.7561.3">Google Chrome Dev (EXE) 145.0.7561.3 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.