Chrome is widely deployed; an RCE that escapes the sandbox can lead to widespread host compromise and is organization‑wide newsworthy.
CVE-2026-118306
Chrome FileSystem memory corruption enables remote code execution outside sandbox.
Is CVE-2026-118306 being exploited?
Not confirmed. CVE-2026-118306 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-118306?
CVE-2026-118306 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-118306?
Yes. A fix has been recorded for CVE-2026-118306. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-118306 affect?
CVE-2026-118306 affects Google Chrome prior to 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-118306?
Update Chrome to 156.0.8078.73+ immediately; enforce auto-updates and restrict untrusted web content.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution via crafted HTML; attacker can run arbitrary code outside Chrome's sandbox on victim 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.