Skip to content
major vulnerability· requires attention

Remote code execution in widely used Google Chrome PDF handling; affects enterprise endpoints and web attack surface, likely to be prioritized by IT teams.

Applications

CVE-2026-106421

8.8
High
EPSS n/aPatch availableOct 8, 2026

Use-after-free in Chrome PDF allows remote code execution in browser sandbox.

common questions

Is CVE-2026-106421 being exploited?

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

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

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

What does CVE-2026-106421 affect?

CVE-2026-106421 affects Google Chrome < 155.0.8059.39, Chrome Desktop (Windows/macOS/Linux). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-106421?

Update Chrome to 155.0.8059.39+ immediately; restrict untrusted PDFs until patched.

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.39Chrome Desktop (Windows/macOS/Linux)
impact

Remote code execution in Chrome's PDF handler via crafted HTML/PDF; attacker can execute arbitrary code in browser and may pivot if sandbox escape occurs.

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