Six Zero-Days in Nine Months: Inside CVE-2026-85046, the Type-Confusion Bug That Put Every Chrome User on a CISA Clock

For the sixth time this year, Google has told Chrome users to stop what they are doing and update their browser. On Thursday, September 4, 2026, the company shipped Chrome 152 security updates resolving 12 vulnerabilities — and one of them, tracked as CVE-2026-85046, is already being exploited in the wild. Within hours, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added the flaw to its Known Exploited Vulnerabilities (KEV) catalog, starting a two-week countdown for every federal civilian agency to patch or explain why they haven’t.

It is a familiar rhythm by now, and that is precisely what makes it unsettling.

What Happened

The vulnerability is a type confusion bug in V8, the JavaScript and WebAssembly engine that powers Chrome — the same engine at the heart of Microsoft Edge, Brave, Opera, and Vivaldi. According to the CVE record, the flaw “allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page.” It carries a CVSS severity score of 8.8, firmly in the high-severity band, and affects all Chrome versions prior to 152.0.7977.82.

The discoverer is independent security researcher Salvatore Gulizia, who reported it responsibly on August 4, 2026, and earned a $1,000 bug bounty. In a technical write-up, Gulizia explained the root cause: a bug in V8’s compilers causes an array containing PACKED_ELEMENTS to receive the map PACKED_SMI_ELEMENTS — a mismatch of internal type metadata that an attacker can escalate into arbitrary read and write primitives on the JavaScript heap.

For the non-expert, the practical translation is simple: a malicious web page you merely visit — no download, no click-through, no permissions prompt — could hijack the renderer process of your browser. The sandbox still contains the blast radius, but sandbox escapes are routinely chained with renderer bugs like this one, which is why Google treats in-the-wild exploitation as a five-alarm event.

Google acknowledged that “an exploit for CVE-2026-85046 exists in the wild” but, following standard procedure, withheld all details about the attacks — who is behind them, what sectors are being targeted, and how the exploit is delivered. That information typically stays sealed until the majority of the install base has updated, to avoid handing a working recipe to other threat actors.

The Patch and the Deadline

Fixed versions are 152.0.7977.82/.83 for Windows and macOS, and 152.0.7977.82 for Linux. Users can update via More > Help > About Google Chrome, then relaunch. Because Chrome normally auto-updates in the background, most people will be protected within days without doing anything — but the staggered rollout is exactly the window attackers live in.

CISA’s KEV addition on September 4 imposes a hard deadline of September 18, 2026 for Federal Civilian Executive Branch (FCEB) agencies to remediate. While the mandate formally binds only federal agencies, the KEV catalog long ago became the de facto patch-priority list for enterprises worldwide; vulnerability management teams outside government treat a KEV entry as a signal that exploitation is not hypothetical.

Users of other Chromium-based browsers — Edge, Brave, Opera, Vivaldi — inherit the same underlying bug and should apply their vendor’s updates as they become available.

Six in Nine Months

The most striking number in this story is the tally: CVE-2026-85046 is the sixth actively exploited Chrome zero-day patched in 2026, joining CVE-2026-2441, CVE-2026-3909, CVE-2026-3910, CVE-2026-5281, and CVE-2026-11645. Five of the six have been V8 engine flaws — type confusions, out-of-bounds reads and writes, and related memory-corruption classes.

That pace continues a multi-year trend. Chrome logged 15 exploited zero-days in 2025 and 9 in 2024, and 2026 is on track to land in the same range. Two forces explain it. First, Chrome’s scale — billions of users across every operating system — makes it the highest-value browser target on earth, attractive to both criminal crews and commercial spyware vendors. Second, V8 itself: a just-in-time compiler doing aggressive speculative optimization on untrusted code is an inherently sharp-edged attack surface, and every optimization pass is a fresh opportunity for the compiler and the runtime to disagree about what type a value is.

Notably, the incentive structure around V8 research has industrialized. Just weeks ago, OpenAI’s specialized cybersecurity model GPT-5.6-Cyber demonstrated it could find previously unknown V8 vulnerabilities on its own — including one patched as CVE-2026-15903. When both dedicated human researchers and now AI systems are systematically mining the same engine, the discovery rate climbs, and the window between a bug’s introduction and its exploitation shrinks.

Why Type Confusion Keeps Winning

Type confusion is a recurring champion in V8’s vulnerability history, and CVE-2026-85046 is a textbook case. V8’s optimizing compilers make assumptions about the shapes of objects — their “maps” in V8 parlance — to generate fast machine code. When a compiler mislabels an array of general objects (PACKED_ELEMENTS) as holding only small integers (PACKED_SMI_ELEMENTS), subsequent optimized code treats pointers as integers, or integers as pointers. An attacker who controls the array’s contents then controls what the engine reads and writes, and from there it is a short step to full read/write primitives on the heap.

Defenses exist — sandboxing, site isolation, speculative-execution mitigations — and they demonstrably raise the cost of a working exploit chain. But they raise the cost rather than eliminate the possibility, and the steady drumbeat of six zero-days a year shows the economics still favor attackers with patience and budget.

What to Do Now

The guidance is boring because it works:

1. Update Chrome today. Help > About Google Chrome. If you are already on 152.0.7977.82 or later, you are covered for this flaw.
2. Update your Chromium-based browsers too. The V8 flaw is inherited; only the patch timing differs by vendor.
3. Enterprise fleets should prioritize against KEV. If your organization maps federal timelines, September 18 is the drop-dead date; treat it as the latest acceptable patch date, not the target.
4. Watch for the technical details drop. Google typically publishes exploit details and root-cause analyses weeks after mass adoption. When the write-up lands, expect detection engineers to publish Snort/Suricata and EDR hunt rules — worth reviewing if you run a security operations team.

One more thing worth noting: the bounty here was $1,000. For a weaponized-quality V8 exploit — a bug class that trades for seven figures on the gray market — the gap between Google’s reward and the black-market price remains enormous, and it is a quiet structural reason why in-the-wild zero-days keep arriving. Researchers like Gulizia who choose responsible disclosure are effectively donating the difference. The sixth zero-day of 2026 is patched, but the arithmetic that produces the seventh is unchanged.