Skip to content
major vulnerability· requires attention

Widely used browser (Google Chrome) with a remote code execution flaw; high CVSS and broad user base warrants organization-wide attention.

Applications

CVE-2026-106252

8.8
High
EPSS 0.27%Patch availableOct 7, 2026

Chrome Fonts RCE via crafted HTML in versions before 155.0.8059.39.

common questions

Is CVE-2026-106252 being exploited?

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

How severe is CVE-2026-106252?

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

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

What does CVE-2026-106252 affect?

CVE-2026-106252 affects Google Chrome <155.0.8059.39 (Desktop). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-106252?

Update Chrome to 155.0.8059.39 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 <155.0.8059.39 (Desktop)
impact

Remote code execution in Chrome renderer via crafted HTML, allowing arbitrary code in browser sandbox; may enable data theft or further compromise if chained.

action required

Immediate action required

affected versions
Google Chrome
  • affected< 155.0.8059.39

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