CVE-2026-126910: Chrome V8 PoC Published

Security researchers have published a proof-of-concept exploit for a high-severity flaw in Google Chrome's V8 JavaScript engine, just three days after Google patched it. The code, uploaded to GitHub on 15 November 2026, was built in part from Google's own regression tests, showing how the tests shipped with a patch can speed up work on an exploit.
The flaw, tracked as CVE-2026-126910, is a type confusion bug in Maglev, the middle tier of V8's just-in-time compiler. It carries a CVSS 3.1 score of 8.8, rated high. The vulnerability description says a remote attacker could execute arbitrary code inside the browser sandbox through a crafted web page, although a second flaw, a sandbox escape, would be needed for a full compromise of the machine.
Built from Google's own patch tests
At 02:23 UTC on 15 November, a GitHub account named Abraxas Labs uploaded the repository abraxas/chrome-v8-maglev-literal-stale, a proof of concept for the flaw. Analysis of the code found that it derives in part from the regression tests Google engineers included in the patch released on 12 November, which moved Chrome to version 157.0.8103.78.
Regression tests are small programs that prove a bug is fixed, and they are routinely shipped with open-source patches. In this case they gave researchers a head start: the tests showed exactly which behaviour had changed, and the proof of concept was reconstructed from them. The same account published six other repositories for vulnerabilities fixed in the same Chrome release.
What the proof of concept can and cannot do
The author is clear about the limits of the code. The readme states that the package is the stale load, not a shell, and that no attempt had been made to turn the flaw into code execution. The proof of concept also needs developer flags to switch on the debugging command that forces Maglev to take over, so it is not a ready-made attack against ordinary users.
Even so, the publication matters. It puts working code for a fresh browser flaw in public at a time when many users have not yet updated, and it gives other researchers a starting point for building a fuller exploit. The original Chromium bug report, issue 574059463, is closed to the public. The patch was credited to V8 engineer Marja Hölttä, with review by Darius Mercadier.
Update Chrome and check Electron apps
Google fixed the flaw in Chrome 157.0.8103.78, part of a release that patched 83 security vulnerabilities, including five rated critical. There is no evidence of exploitation in the wild, and the flaw is not on the US CISA list of exploited vulnerabilities. The estimated chance of attack in the next 30 days is low, at around a third of one per cent.
Users should check they are on Chrome 157.0.8103.78 or later rather than waiting for the automatic rollout, which Google says will take days or weeks. Applications built on Electron, which embed Chromium, remain vulnerable until their developers ship their own updates, so desktop apps such as chat and editing tools need attention too. More detail is in the analysis at Deaf News.