Google Chrome is ubiquitous; an RCE that escapes the sandbox can enable host compromise across enterprises and consumer devices, requiring org-wide mitigation.
CVE-2026-118316
Chrome V8 remote code execution via crafted HTML escaping sandbox.
Is CVE-2026-118316 being exploited?
Not confirmed. CVE-2026-118316 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-118316?
CVE-2026-118316 is rated Critical with a CVSS score of 9.6. 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-118316?
Yes. A fix has been recorded for CVE-2026-118316. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-118316 affect?
CVE-2026-118316 affects Google Chrome <156.0.8078.73 (Windows), Google Chrome <156.0.8078.73 (macOS), Google Chrome <156.0.8078.73 (Linux), Google Chrome <156.0.8078.73 (ChromeOS). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-118316?
Update Chrome to 156.0.8078.73 or later; enforce safe browsing and endpoint detection.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution outside Chrome sandbox via crafted HTML, enabling arbitrary code execution, data access, and persistence on affected hosts.
Immediate action required
- 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.