Chrome's zero-day Whac-A-Mole continues with fifth exploited bug of the year
Google confirmed that the vulnerability is being exploited in the wild, but has disclosed little beyond the bare technical details.The company patched the issue in the latest Stable Channel releases for Windows, macOS, and Linux. It also awarded a $55,000 bounty to the researcher using the handle "303f06e3," who reported the bug on April 27. REG AD googletag.cmd.push(function() { googletag.display('labrador/thereg/article/desktop/b'); }); The reward suggests Google viewed the report as potentially serious, particularly given its location in V8, the JavaScript engine at the heart of Chrome.
- ▪Google confirmed that the vulnerability is being exploited in the wild, but has disclosed little beyond the bare technical details.The company patched the issue in the latest Stable Channel releases for Windows, macOS, and Linux.
- ▪It also awarded a $55,000 bounty to the researcher using the handle "303f06e3," who reported the bug on April 27.
- ▪REG AD googletag.cmd.push(function() { googletag.display('labrador/thereg/article/desktop/b'); }); The reward suggests Google viewed the report as potentially serious, particularly given its location in V8, the JavaScript engine at the hear
The Register publishes from United Kingdom and files mainly under tech. We currently carry 341 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | theregister |
| Canonical URL | https://www.theregister.com/security/2026/06/09/chromes-zero-day-whac-a-mole-continues-with-fifth-exploited-bug-of-the-year/5252689 |
| Publication time | Tue, 09 Jun 2026 14:15:00 +0200 |
| Retrieval time | 2026-06-09T13:54:22.101Z |
| Last seen | 2026-06-09T13:54:22.101Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | hzkbv8TrAtmN |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
(function() { let windowUrl = window.location.href; windowUrl = windowUrl.substring(windowUrl.indexOf('?') + 1); let messageElement = document.querySelector('.shareableMessage'); if (windowUrl && windowUrl.includes('code') && windowUrl.includes('expires')) { messageElement.style.display = 'block'; } })(); SECURITY Chrome's zero-day Whac-A-Mole continues with fifth exploited bug of the year Google paid researcher a tidy $55K bounty for its discovery Carly Page Carly Page Published tue 9 Jun 2026 // 13:15 UTC Google has fixed its fifth actively exploited Chrome zero-day of 2026, and this one earned its finder a $55,000 bounty.The flaw, tracked as CVE-2026-11645, is an out-of-bounds memory access bug in Chrome's V8 JavaScript engine.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at theregister.
Discussion
0 commentsMore from theregister
