Google · Memory corruption
Buffer overflow in Media in Google Chrome prior to 152.0.7977.65 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page
At a glance
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 2 Dec?
Next steps
- Confirm whether this affects systems or suppliers in your estate
No technical write-up beyond the summary below yet.
Next steps
- Review the advisory against your asset inventory and patch cadence
Summary
- Exploitation in the wild is not confirmed; treat this as a prioritisation signal.
Read the original reportMicrosoft Security Update Guide RSS(opens in a new tab)
Products and services involved
- Google Chrome93% match confidence · CVE-2026-79231
Pulse
Last checked 6d ago · Recheck overdue since 3 Nov 2026, 07:03 UK time
- Story28 Oct 2026, 20:58 UK time · 28 Oct
Linked reporting from Microsoft Security Update Guide RSS (vendor psirt).
Read source (Microsoft Security Update Guide RSS) - Signal2 Nov 2026, 07:03 UK time · 6d ago
in the next 30 days first recorded at 0.5% (lower likelihood signal, not confirmed exploitation).
2 entries so far. The timeline chart appears once this story has more history.
Sources
Chromium: CVE-2026-79231 Buffer overflow in Media
How we know
Statements extracted from sources. Higher confidence means stronger corroboration.
- ClaimedHeadline60% confidence
Buffer overflow in Media in Google Chrome prior to 152.0.7977.65 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page
- ConfirmedCVE identifier95% confidence
Event involves CVE-2026-79231