Skip to content
major vulnerability· requires attention

High-severity remote code execution in widely used Google Chrome V8; affects large installed base and warrants org-wide rollout of updates.

Web

CVE-2026-102302

8.8
High
EPSS n/aPatch availableSep 30, 2026

V8 buffer overflow allows remote code execution in Chrome via crafted HTML

common questions

Is CVE-2026-102302 being exploited?

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

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

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

What does CVE-2026-102302 affect?

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

What should I do about CVE-2026-102302?

Update Chrome to 154.0.8037.92 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 (desktop) <154.0.8037.92Chromium-based browsers using affected V8
impact

Remote arbitrary code execution in Chrome renderer (inside sandbox) via crafted HTML; sandbox escape could enable full host compromise.

action required

Immediate action required

affected versions
Google Chrome
  • affected< 154.0.8037.92

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