Skip to content
major vulnerability· requires attention

Remote RCE in a widely used browser (Google Chrome) that warrants org-wide patching and will be broadly noticed.

Applications

CVE-2026-103625

8.8
High
EPSS n/aPatch availableOct 3, 2026

Type-confusion in V8 allows remote code execution in Chrome renderer (pre-154.0.8037.97).

common questions

Is CVE-2026-103625 being exploited?

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

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

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

What does CVE-2026-103625 affect?

CVE-2026-103625 affects Google Chrome <154.0.8037.97, Chromium-based browsers (potentially). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-103625?

Update Chrome to 154.0.8037.97+ immediately; deploy via managed update channels.

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.97Chromium-based browsers (potentially)
impact

Remote code execution in Chrome V8 via crafted HTML, allowing arbitrary code in sandboxed renderer and potential browser compromise.

action required

Immediate action required

affected versions
Google Chrome
  • affected< 154.0.8037.97

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