Skip to content
major vulnerability· requires attention

Remote RCE in Google Chrome's V8 affects a ubiquitous browser used across organizations; endpoint compromise risk warrants broad IT notification.

Applications

CVE-2026-15132

8.8
High
EPSS 0.45%Patch availableJul 9, 2026

Uninitialized-use in V8 allows remote code execution in Chrome (<150.0.7871.115).

common questions

Is CVE-2026-15132 being exploited?

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

How severe is CVE-2026-15132?

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

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

What does CVE-2026-15132 affect?

CVE-2026-15132 affects Google Chrome <150.0.7871.115, V8 JavaScript engine (Chromium-based browsers may be affected). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-15132?

Update Chrome to 150.0.7871.115 or later on all endpoints immediately.

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.115V8 JavaScript engine (Chromium-based browsers may be affected)
impact

Remote arbitrary code execution inside Chrome sandbox via crafted HTML, enabling endpoint compromise or further pivoting.

action required

Immediate action required

affected versions
Google Chrome
  • affected< 150.0.7871.115

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