Skip to content
major vulnerability· requires attention

Browser V8 RCE in Google Chrome is widely used and enables remote code execution from web content; affects large user base and warrants org-wide notification.

Web

CVE-2026-118320

8.8
High
EPSS n/aPatch availableOct 28, 2026

V8 memory corruption in Chrome allows sandboxed remote code execution via crafted web page.

common questions

Is CVE-2026-118320 being exploited?

Not confirmed. CVE-2026-118320 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-118320?

CVE-2026-118320 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-118320?

Yes. A fix has been recorded for CVE-2026-118320. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-118320 affect?

CVE-2026-118320 affects Google Chrome <156.0.8078.73 (desktop), Chromium-based browsers (likely). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-118320?

Update Chrome to 156.0.8078.73 or later immediately

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Google Chrome <156.0.8078.73 (desktop)Chromium-based browsers (likely)
impact

Remote code execution in Chrome's V8 engine via a crafted HTML page, allowing attacker-controlled code to run inside the browser sandbox.

action required

Immediate action required

affected versions
Google Chrome
  • 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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved