Skip to content
major vulnerability· requires attention

Affects widely used Google Chrome V8 engine; remote code execution in browsers can compromise endpoints across organizations and warrants org-wide action.

Applications

CVE-2026-16418

8.8
High
EPSS 0.33%Patch availableJul 24, 2026

V8 stack overflow allows remote arbitrary code execution in Chrome <150.0.7871.182

common questions

Is CVE-2026-16418 being exploited?

Not confirmed. CVE-2026-16418 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.33% probability of exploitation in the next 30 days.

How severe is CVE-2026-16418?

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

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

What does CVE-2026-16418 affect?

CVE-2026-16418 affects Google Chrome <150.0.7871.182, Chromium-based browsers using affected V8 builds. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-16418?

Update Chrome to 150.0.7871.182 or later across your fleet; block untrusted web content.

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

executive summary
technical analysis
affected
Google Chrome <150.0.7871.182Chromium-based browsers using affected V8 builds
impact

Remote arbitrary code execution via crafted HTML in V8 (browser sandbox), enabling browser compromise, data theft, or persistence.

action required

Immediate action required

affected versions
Google Chrome
  • affected< 150.0.7871.182

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