Google · Memory corruption
Use after free in WebXR in Google Chrome prior to 157.0.8103.38 allowed a remote attacker leveraging social engineering to execute arbitrary code outside the sandbox via a crafted…
At a glance
~0.4% 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
There is no written leader briefing for this story yet. These questions come from the facts we hold.
Questions to ask IT
- Do we run Google Chrome, and which versions?
- If it is not yet patched, what mitigation is in place, and will the fix be done by 7 Dec?
Next steps
- Confirm whether this affects systems or suppliers in your estate
Vulnerability facts
Full CVE detail CVE-2026-121076- 9.6 · CriticalExploitable 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, and it can reach beyond the vulnerable system.CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
- Not listed
- ~0.3% estimated chance of attack in 30 days
- Before 157.0.8103.38
- 157.0.8103.38
These facts are for CVE-2026-121076. This event covers 9 more CVEs, each with its own record. Versions are as the CVE record states them; check the vendor advisory before planning a fix.
- M-156, ChromeOS version 16836.32.0 (Browser version 156.0.8078.93)has rolled out to ChromeOS devices on the Stable channel. If you find new issues, please let us know one of the following ways: File a bug Visit our ChromeOS communities.
Next steps
- Review the advisory against your asset inventory and patch cadence
Summary
- M-156, ChromeOS version 16836.32.0 (Browser version 156.0.8078.93)has rolled out to ChromeOS devices on the Stable channel.
- CVE-2026-121076 has an estimated ~0.3% chance of attack in 30 days (27.3th percentile) as of 2026-11-06 — probability signal, not confirmed exploitation
Products and services involved
- Google Chrome93% match confidence · CVE-2026-121076
Part of The New Social Engineering Playbook Starts With Reconnaissance
Pulse
Last change yesterday · Recheck overdue since 8 Nov 2026, 02:32 UK time
- Story7 Nov 2026, 02:32 UK time · yesterday
Linked reporting from Chrome Releases (vendor psirt).
Read source (Chrome Releases)
1 entry so far. The timeline chart appears once this story has more history.
Sources
- Chrome ReleasesVendor
Stable Channel Update for ChromeOS / ChromeOS Flex
How we know
Statements extracted from sources. Higher confidence means stronger corroboration.
- ClaimedHeadline60% confidence
Use after free in WebXR in Google Chrome prior to 157.0.8103.38 allowed a remote attacker leveraging social engineering to execute arbitrary code outside the sandbox via a crafted…
- ProbableSummary fact75% confidence
M-156, ChromeOS version 16836.32.0 (Browser version 156.0.8078.93)has rolled out to ChromeOS devices on the Stable channel. If you find new issues, please let us know one of the following ways: File a bug Visit our ChromeOS communities
- ConfirmedCVE identifier95% confidence
Event involves CVE-2026-121076
- ConfirmedEstimated attack likelihood95% confidence
CVE-2026-121076 has an estimated ~0.3% chance of attack in 30 days (27.3th percentile) as of 2026-11-06 — probability signal, not confirmed exploitation
- ConfirmedCVE identifier95% confidence
Event involves CVE-2026-121135
- ConfirmedEstimated attack likelihood95% confidence
CVE-2026-121135 has an estimated ~0.3% chance of attack in 30 days (17.1th percentile) as of 2026-11-06 — probability signal, not confirmed exploitation
- ConfirmedCVE identifier95% confidence
Event involves CVE-2026-121141
- ConfirmedCVE identifier95% confidence
Event involves CVE-2026-121184
- ConfirmedEstimated attack likelihood95% confidence
CVE-2026-121184 has an estimated ~0.4% chance of attack in 30 days (29.8th percentile) as of 2026-11-06 — probability signal, not confirmed exploitation
- ConfirmedCVE identifier95% confidence
Event involves CVE-2026-121201
- ConfirmedEstimated attack likelihood95% confidence
CVE-2026-121201 has an estimated ~0.4% chance of attack in 30 days (31th percentile) as of 2026-11-06 — probability signal, not confirmed exploitation
- ConfirmedCVE identifier95% confidence
Event involves CVE-2026-121208

