Skip to content
major vulnerability· requires attention

Chrome is ubiquitous; a remote RCE in V8 can lead to widespread endpoint compromise and will be broadly relevant to IT/security teams.

Applications

CVE-2026-110919

8.8
High
EPSS 0.22%Patch availableOct 17, 2026

Use-after-free in V8 allows remote code execution in Chrome <155.0.8059.84

common questions

Is CVE-2026-110919 being exploited?

Not confirmed. CVE-2026-110919 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. EPSS currently estimates a 0.22% probability of exploitation in the next 30 days.

How severe is CVE-2026-110919?

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

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

What does CVE-2026-110919 affect?

CVE-2026-110919 affects Google Chrome for Desktop (<155.0.8059.84) - Windows/Mac/Linux. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-110919?

Update Chrome to 155.0.8059.84+ immediately and enforce auto-update on endpoints.

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

executive summary
technical analysis
affected
Google Chrome for Desktop (<155.0.8059.84) - Windows/Mac/Linux
impact

Remote arbitrary code execution inside Chrome's sandbox via crafted HTML, allowing attacker-controlled code in the browser process.

action required

Immediate action required

affected versions
Google Chrome
  • affected< 155.0.8059.84

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