Google · Memory corruption
Out of bounds read in Compositing in Google Chrome prior to 157.0.8103.78 allowed a remote attacker who had compromised the renderer process to read memory outside the sandbox via…
At a glance
~0.2% 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
- IT leaders should verify if any systems are running Google Chrome versions prior to 157.0.8103.78 and apply updates promptly.
- Businesses using Microsoft Edge (Chromium-based) should ensure they are receiving Chromium updates to mitigate this vulnerability.
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-126913- 3.4 · LowExploitable over the network without any account, under specific conditions, but only if a user takes an action, such as opening a file or link. Low impact on confidentiality, and it can reach beyond the vulnerable system.CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:N/A:N
- Not listed
- ~0.2% 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 affects Google Chrome versions prior to 157.0.8103.78 and allows memory reading outside the sandbox via a compromised renderer process.
- Microsoft Edge (Chromium-based) incorporates Chromium fixes that address this vulnerability.
- CVE-2026-126913 has an estimated 0.2% chance of attack in 30 days (6.5th percentile) as of 2026-11-13 — this is a probability signal, not confirmed exploitation.
Next steps
- Review the advisory against your asset inventory and patch cadence
Summary
- A vulnerability in Google Chrome's Compositing component allowed a remote attacker to read memory outside the sandbox after compromising the renderer process.
- Microsoft Edge (Chromium-based) addresses this vulnerability through Chromium updates.
Read the original reportMicrosoft Security Update Guide RSS(opens in a new tab)
Products and services involved
- Microsoft Edge98% match confidence · CVE-2026-126913
- Google Chrome98% match confidence · CVE-2026-126913
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-126913: Out of bounds read
How we know
Statements extracted from sources. Higher confidence means stronger corroboration.
- ClaimedHeadline60% confidence
Out of bounds read in Compositing in Google Chrome prior to 157.0.8103.78 allowed a remote attacker who had compromised the renderer process to read memory outside the sandbox via…
- 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-126913
- ConfirmedEstimated attack likelihood95% confidence
CVE-2026-126913 has an estimated ~0.2% chance of attack in 30 days (6.5th percentile) as of 2026-11-13 — probability signal, not confirmed exploitation