Skip to content
major vulnerability· requires attention

Chrome is widely deployed; a remote code execution in V8 browser engine can broadly impact endpoints and is high-profile, requiring organization-wide action.

Applications

CVE-2026-102323

8.8
High
EPSS n/aPatch availableSep 30, 2026

Type-confusion in V8 enables remote code execution in Chrome sandbox.

common questions

Is CVE-2026-102323 being exploited?

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

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

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

What does CVE-2026-102323 affect?

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

What should I do about CVE-2026-102323?

Update Chrome to 154.0.8037.92 or later immediately; enforce enterprise updates.

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

executive summary
technical analysis
affected
Google Chrome < 154.0.8037.92Chromium-based browsers using same V8
impact

Remote arbitrary code execution in Chrome renderer via crafted HTML, allowing attacker-controlled code to run inside the browser sandbox.

action required

Patch when possible

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