Chromium: CVE-2026-4680 Use after free in FedCM
CVE-2026-4680 is fixed in 11 products on 2 platforms, first by Google Chrome Dev (EXE) 147.0.7695.0, released February 19, 2026. It is not reported as exploited. Patch Radar priority: High.
<p>This CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see <a href="https://chromereleases.googleblog.com/2026">Google Chrome Releases</a> for more information.</p>
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Windows apps | |||
| Google Chrome | 156.0.8078.80 | Google Chrome 156.0.8078.80 | Oct 29, 2026 |
| Google Chrome (EXE) | 146.0.7680.165 | Google Chrome (EXE) 146.0.7680.165 | Mar 21, 2026 |
| Google Chrome Beta | 158.0.8127.2 | Google Chrome Beta 158.0.8127.2 | Oct 28, 2026 |
| Google Chrome Beta (EXE) | 147.0.7727.3 | Google Chrome Beta (EXE) 147.0.7727.3 | Mar 11, 2026 |
| Google Chrome Dev | 159.0.8130.0 | Google Chrome Dev 159.0.8130.0 | Oct 30, 2026 |
| Google Chrome Dev (EXE) | 147.0.7695.0 | Google Chrome Dev (EXE) 147.0.7695.0 | Feb 19, 2026 |
| Microsoft Edge | 146.0.3856.84 | Microsoft Edge 146.0.3856.84 | Mar 26, 2026 |
| Microsoft Edge Beta | 151.0.4129.59 | Microsoft Edge Beta 151.0.4129.59 | Jul 31, 2026 |
| Microsoft Edge Dev | 152.0.4167.0 | Microsoft Edge Dev 152.0.4167.0 | Jul 20, 2026 |
| Microsoft Edge WebView2 Runtime | 146.0.3856.84 | Microsoft Edge WebView2 Runtime 146.0.3856.84 | Mar 26, 2026 |
| Linux | |||
| chromium · Debian 12.15 (bookworm) | 146.0.7680.164-1~deb12u1 | DEBIAN-CVE-2026-4680 | Mar 24, 2026 |
| chromium · Debian 13.5 (trixie) | 146.0.7680.164-1~deb13u1 | DEBIAN-CVE-2026-4680 | Mar 24, 2026 |
| chromium · Debian 14 | 146.0.7680.164-1 | DEBIAN-CVE-2026-4680 | Mar 24, 2026 |
| chromium · opensuse-leap 16.0 | 146.0.7680.177-bp160.1.1 | OPENSUSE-SU-2026:20460-1 | Aug 31, 2026 |
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.