Skip to content
major vulnerability· requires attention

Remote RCE in PDFium affecting widely deployed Google Chrome desktop; impacts large numbers of enterprise endpoints and requires immediate org-wide updates.

Applications

CVE-2026-95338

8.8
High
EPSS n/aPatch availableSep 30, 2026

PDFium use-after-free in Chrome enables remote code execution via crafted PDF.

common questions

Is CVE-2026-95338 being exploited?

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

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

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

What does CVE-2026-95338 affect?

CVE-2026-95338 affects Google Chrome (desktop) versions prior to 154.0.8037.57 — Windows, macOS, Linux. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-95338?

Update Chrome to 154.0.8037.57 or later immediately; restrict/unblock PDFs from untrusted sources.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Google Chrome (desktop) versions prior to 154.0.8037.57 — Windows, macOS, Linux
impact

Remote code execution in Chrome's PDFium renderer via crafted PDF, enabling arbitrary code execution in the browser sandbox and potential compromise of the host.

action required

Immediate action required

affected versions
Google Chrome
  • affected< 154.0.8037.57

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