Google · Memory corruption
Memory corruption in Payments in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page
At a glance
Medium rather than High: exposure is scored at a default because we cannot see your systems or suppliers.
Briefing
- IT leaders should verify if Google Chrome versions prior to 156.0.8078.73 are in use.
- Businesses using Microsoft Edge should confirm Chromium updates address this vulnerability.
Questions to ask IT
- Do we run Google Chrome and Microsoft Edge, and is every instance on version 156.0.8078.73 or later?
- If it is still not patched, what mitigation is in place, and what is holding the fix up?
Next steps
- Confirm whether this affects systems or suppliers in your estate
Vulnerability facts
Full CVE detail CVE-2026-118349- 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 156.0.8078.73
- 156.0.8078.73
Versions are as the CVE record states them; check the vendor advisory before planning a fix.
- Google Chrome versions prior to 156.0.8078.73 are affected by memory corruption in the Payments component.
- Microsoft Edge (Chromium-based) incorporates Chromium fixes for this vulnerability.
Next steps
- Review the advisory against your asset inventory and patch cadence
Summary
- A vulnerability in Google Chrome's Payments component allowed remote code execution via a crafted HTML page.
- 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
- Google Chrome93% match confidence · CVE-2026-118349
- Microsoft Edge98% match confidence · CVE-2026-118349
Pulse
Last change 31 Oct · Recheck overdue since 1 Nov 2026, 18:25 UK time
- Story31 Oct 2026, 18:25 UK time · 31 Oct
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-118349 Memory corruption in Payments
How we know
Statements extracted from sources. Higher confidence means stronger corroboration.
- ClaimedHeadline60% confidence
Memory corruption in Payments in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to 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-118349