Skip to content
major vulnerability· requires attention

Widespread browser (Google Chrome) vulnerability enabling site-isolation bypass and cross-origin data exposure; affects many organizations and requires prompt remediation.

Applications

CVE-2026-106271

8.1
High
EPSS 0.23%Patch availableOct 9, 2026

Chrome Workers auth bypass lets compromised renderer bypass site isolation via crafted PDF

common questions

Is CVE-2026-106271 being exploited?

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

How severe is CVE-2026-106271?

CVE-2026-106271 is rated High with a CVSS score of 8.1. 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-106271?

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

What does CVE-2026-106271 affect?

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

Update Chrome to 155.0.8059.39+ immediately; restrict untrusted PDFs.

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

A compromised renderer plus crafted PDF can bypass site isolation to read/exfiltrate cross-origin data and tokens.

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