Skip to content
major vulnerability· requires attention

Remote code execution in Google Chrome PDF engine affects a ubiquitous browser on Windows; widespread impact on endpoint security and likely to be prioritized by orgs.

Applications

CVE-2026-87585

8.8
High
EPSS 0.28%Patch availableSep 10, 2026

PDFium double-free in Chrome allows remote code execution via crafted PDF on Windows

common questions

Is CVE-2026-87585 being exploited?

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

How severe is CVE-2026-87585?

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

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

What does CVE-2026-87585 affect?

CVE-2026-87585 affects Google Chrome on Windows (prior to 153.0.8010.36). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-87585?

Update Chrome to 153.0.8010.36+ immediately; block/avoid 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 on Windows (prior to 153.0.8010.36)
impact

Remote code execution in Chrome via crafted PDF, enabling arbitrary code execution inside the browser sandbox and potential compromise of user endpoints.

action required

Immediate action required

affected versions
Google Chrome
  • affected< 153.0.8010.36

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