Skip to content
major vulnerability· requires attention

Remote code execution in Google Chrome's V8 affects a ubiquitous browser used enterprise-wide; high-impact and broadly relevant to IT teams.

Applications

CVE-2026-95306

8.8
High
EPSS n/aPatch availableOct 1, 2026

Type confusion in V8 enables remote code execution in Google Chrome (<154.0.8037.57).

common questions

Is CVE-2026-95306 being exploited?

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

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

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

What does CVE-2026-95306 affect?

CVE-2026-95306 affects Google Chrome (desktop) prior to 154.0.8037.57, V8 JavaScript engine. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-95306?

Update Chrome to 154.0.8037.57+ immediately and enforce auto-updates.

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

executive summary
technical analysis
affected
Google Chrome (desktop) prior to 154.0.8037.57V8 JavaScript engine
impact

Remote arbitrary code execution in Chrome's V8 engine inside the renderer sandbox via crafted HTML, enabling browser compromise and potential data exposure.

action required

Patch when possible

affected versions
Google Chrome
  • affected< 154.0.8037.57

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