Chrome is ubiquitous; a V8 remote code execution bug can affect many endpoints and is high-impact for enterprises.
CVE-2026-118359
V8 memory corruption in Chrome enables remote code execution in the browser sandbox
Is CVE-2026-118359 being exploited?
Not confirmed. CVE-2026-118359 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.
How severe is CVE-2026-118359?
CVE-2026-118359 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-118359?
Yes. A fix has been recorded for CVE-2026-118359. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-118359 affect?
CVE-2026-118359 affects Google Chrome <156.0.8078.73 (Windows, macOS, Linux). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-118359?
Update Chrome to 156.0.8078.73 or later immediately via enterprise update channels.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution in Chrome via crafted HTML, allowing arbitrary code execution inside the browser sandbox.
Patch when possible
- affected< 156.0.8078.73
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.