Google · Memory corruption
Memory corruption in V8 in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page
At a glance
~0.3% estimated chance of attack in 30 days. Exploitation not confirmed.
Low rather than Medium: UK relevance is 40 of 100, little UK-specific signal so far.
Briefing
- Organisations should verify if any affected Chrome versions are present in their estate and apply updates promptly.
Questions to ask IT
- Do we run Microsoft Edge and Google Chrome, and is every instance on version 157.0.8103.78 or later?
- If it is not yet patched, what mitigation is in place, and will the fix be done by 13 Dec?
Next steps
- Confirm whether this affects systems or suppliers in your estate
Vulnerability facts
Full CVE detail CVE-2026-126917- 8.8 · HighExploitable over the network without any account, but only if a user takes an action, such as opening a file or link. High impact on confidentiality, integrity and availability.CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- Not listed
- ~0.3% estimated chance of attack in 30 days
- Before 157.0.8103.78
- 157.0.8103.78
- Not linked from the CVE record
Versions are as the CVE record states them; check the vendor advisory before planning a fix.
- The vulnerability is identified as CVE-2026-126917 and involves memory corruption in V8.
- An estimated attack likelihood score indicates a ~0.3% chance of attack in 30 days for CVE-2026-126917 as of 2026-11-13.
Next steps
- Review the advisory against your asset inventory and patch cadence
Summary
- A vulnerability in Google Chrome's V8 engine prior to version 157.0.8103.78 could allow a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page.
- Microsoft Edge (Chromium-based) addresses this vulnerability through its Chromium integration.
Read the original reportMicrosoft Security Update Guide RSS(opens in a new tab)
Products and services involved
- Microsoft Edge98% match confidence · CVE-2026-126917
- Google Chrome98% match confidence · CVE-2026-126917
Pulse
Last change 1h ago · Next recheck 14 Nov 2026, 23:11 UK time
- Story13 Nov 2026, 23:11 UK time · 1h ago
Linked reporting from Microsoft Security Update Guide RSS (vendor psirt).
Read source (Microsoft Security Update Guide RSS)
1 entry so far. The timeline chart appears once this story has more history.
Sources
Chromium CVE-2026-126917: Memory corruption
How we know
Statements extracted from sources. Higher confidence means stronger corroboration.
- ClaimedHeadline60% confidence
Memory corruption in V8 in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page
- ProbableSummary fact75% confidence
Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see [Google Chrome Releases](https://chromereleases.googleblog.com/2026) for more information.
- ConfirmedCVE identifier95% confidence
Event involves CVE-2026-126917
- ConfirmedEstimated attack likelihood95% confidence
CVE-2026-126917 has an estimated ~0.3% chance of attack in 30 days (25.9th percentile) as of 2026-11-13 — probability signal, not confirmed exploitation