Attackers chain V8 Maglev bugs with sandbox escapes against Edge and Chrome builds missing the fix
Microsoft says attackers chained V8 Maglev code-execution bugs with V8 sandbox escapes against Edge and Chrome users who lacked the fixes. Chrome Stable's matching update arrived four days after Edge's, on 8 September.
The Watch · Security desk
1 September: Microsoft confirms active exploitation of a V8 code-execution bug. 2 September: first Edge fix rolls out. 3 September: attackers confirmed also using a V8 sandbox escape. 4 September: Edge sandbox-escape fix rolls out. 8 September: Chrome's corresponding Stable update.
- 2026Microsoft confirms exploitation of V8 code-execution bug, claim 4
- 2026First fix rolls out in Edge 152.0.4191.62, claim 6
- 2026Attackers also using a V8 sandbox escape, confirmed, claim 7
- 2026Edge 152.0.4191.66 rolls out sandbox-escape fix, claim 8
- 2026Chrome's corresponding Stable update, claim 9
| Date | Event | Claim |
|---|---|---|
| September 1, 2026 | Microsoft confirms exploitation of V8 code-execution bug | 4 |
| September 2, 2026 | First fix rolls out in Edge 152.0.4191.62 | 6 |
| September 3, 2026 | Attackers also using a V8 sandbox escape, confirmed | 7 |
| September 4, 2026 | Edge 152.0.4191.66 rolls out sandbox-escape fix | 8 |
| September 8, 2026 | Chrome's corresponding Stable update | 9 |
What happened
- In one recent example, attackers used an N-Day vulnerability in Windows for the final stage.
- On 1 September Microsoft confirmed active exploitation of a V8 code-execution bug whose fix had not yet shipped in Chrome Stable.
- On 3 September Microsoft threat intelligence confirmed attackers were also using a V8 sandbox escape, which prompted a second expedited Edge update.
Why it matters
- exposure A shipped release protects only machines that have received it and restarted the browser, so the vendor's release date understates how long users stay exposed.
- decision Microsoft's named defence is prompt install plus restart, so a fleet's patch deadline has to include the restart.
- precedent A public V8 pull request is input for exploit developers, so every vendor's integrate, validate and ship interval counts as exposure time.
- capability Edge can isolate a single fix and ship it without waiting for its next routine Chromium integration when exploitation is active.
Two of the three stages are browser bugs. Attackers first ran code inside V8 through a flaw in the Maglev compiler, then broke out of V8's internal sandbox while still confined to the renderer [10]. Getting out of the renderer sandbox and onto the operating system took another exploit [10]. In the one recent example Microsoft gives, that last step used a Windows N-Day [11]. The post does not list CVE identifiers, name the Windows flaw, count victims, attribute the activity to an actor or date the public upstream fixes.
Microsoft says it found and disrupted the campaign in early September 2026 [18], with help from Proofpoint and Volexity [1]. It confirmed active exploitation of the V8 code-execution bug on 1 September, when the fix had not yet shipped in Chrome Stable [4]. Edge's first fix began rolling out on 2 September [6]. The sandbox escape was confirmed on 3 September [7], and Edge's second fix began rolling out on 4 September [8]. Each Edge fix started shipping one day after the matching confirmation [21]. Chrome Stable's update came on 8 September [9], four days after Edge [19] and five days after the sandbox escape was confirmed [20].
Edge got its fix out earlier by backporting. It isolated the single change instead of taking all unreleased changes from Chromium's release branch [5].
Microsoft frames the AI link as a possibility. It says the technique is not new, but that the speed and expertise required are changing [14]. It says "Evidence suggests AI may be accelerating this patch-gap abuse" [22], and that AI-assisted analysis and exploit development "could compress work that once took weeks into hours" [23]. The post is a single vendor account of its own response. With no date for the public commits, the interval between a public fix and a working exploit cannot be measured from it. Reading a public pull request to infer the bug is the older method Microsoft describes [13].
For defenders the two gaps are separate. One is the vendor's interval to integrate, validate and ship a fix. The other is the time before a device has the update and the browser has restarted [12]. Microsoft says rollout timing varies by platform and device, and a release date does not mean protection is active everywhere [15]. The defence it names is to install updates promptly and restart when required [16].
What to watch
- Publication of CVE identifiers for the Maglev and V8 sandbox-escape bugs, and of the Windows N-Day used in the final stage.
- Any dated evidence of the gap between a public Chromium commit and a working exploit, which is what would test the AI-acceleration claim.
- Whether other Chromium-based browsers adopt single-fix backports when exploitation is active.
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence50
- Adoption
- Insufficient
- Hype gap+15
- Incentives60
- Confidence55
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
Microsoft Edge Security and Microsoft Threat Intelligence recently disrupted several sustained attack campaigns against Chromium-based browsers, and Microsoft thanks its partners at Proofpoint and Volexity for their contributions.
- [2]
Threat actors are exploiting recently fixed vulnerabilities to target users running versions of Edge and Chrome that have not yet received the fixes.
- [3]
In two exploit chains, attackers paired remote-code-execution vulnerabilities in V8's Maglev compiler with escapes from V8's internal sandbox.
- [4]
On 1 September, Microsoft confirmed active exploitation of a V8 remote-code-execution vulnerability and began an expedited Stable response; the fix had not yet shipped in Chrome Stable.
- [5]
Edge independently isolated and backported the change rather than taking all unreleased changes from Chromium's release branch.
- [6]
The first fix began rolling out in Microsoft Edge 152.0.4191.62 on 2 September.
- [7]
On 3 September, threat intelligence confirmed that attackers were also using an escape from V8's internal sandbox, prompting a second expedited update.
- [8]
Microsoft Edge 152.0.4191.66 began rolling out with the additional sandbox-escape fix on 4 September.
- [9]
Chrome's corresponding Stable update followed on 8 September.
- [10]
The exploit chain had three stages: a remote-code-execution vulnerability in Maglev to execute code inside V8; a sandbox-escape vulnerability to break out of V8's internal sandbox while remaining inside the renderer process; and a further exploit, still required, to escape the renderer sandbox and reach the operating system.
- [11]
In one recent example, attackers used an N-Day vulnerability in Windows for the final stage of the chain.
- [12]
At least two gaps must be closed: the interval between a fix becoming available in Chromium and a browser vendor integrating, validating and shipping it, and the interval between that browser release and the updated version running on a user's device.
- [13]
Once a security-relevant code change is public, attackers can examine the pull request, infer the underlying vulnerability, and develop an exploit that can target browser releases without the fix and devices that have not yet updated or restarted.
- [14]
Patch-gap abuse is not a new technique, but the speed and expertise required is changing.
- [15]
Rollout timing varied by platform and device; a release date does not mean protection is active everywhere, because users still need to receive the update and restart the browser.
- [16]
Microsoft says the most immediate defence remains to install browser updates promptly and restart when required.
- [17]
When active exploitation warrants it, Edge can isolate and expedite an individual fix rather than waiting for the next routine integration of Chromium changes.
- [18]
The exploit campaign was discovered and disrupted by Microsoft in early September 2026.
- [19]
Chrome Stable's corresponding update came four days after Edge 152.0.4191.66 began rolling out.
- [20]
Chrome Stable's corresponding update came five days after threat intelligence confirmed the sandbox escape.
- [21]
Each Edge fix began rolling out one day after the matching confirmation of exploitation.
- [22]
Microsoft wrote: "Evidence suggests AI may be accelerating this patch-gap abuse."
- [23]
Microsoft says AI-assisted analysis and exploit development could compress work that once took weeks into hours, increasing the chance that a usable exploit emerges while either exposure window remains open.
Get this ledger inside ChatGPT. Ask about any of our stories and the answer brings its figure, each claim’s verdict and the sources. Free, no account.
Sources
1 independent publisher whose own reporting we read for this story.
- Microsoft Edge
microsoftedge.github.io
1 article · October 13, 2026
Topics and entities
Follow any of these and your For You feed starts watching them — no settings page required.