Chrome is ubiquitous; this sandbox escape enables host-level code execution from crafted PDFs and poses broad organizational risk requiring immediate attention.
CVE-2026-17803
Chrome Save to Drive sandbox escape via crafted PDF allows host code execution.
Is CVE-2026-17803 being exploited?
Not confirmed. CVE-2026-17803 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.38% probability of exploitation in the next 30 days.
How severe is CVE-2026-17803?
CVE-2026-17803 is rated Critical with a CVSS score of 9.6. 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-17803?
Yes. A fix has been recorded for CVE-2026-17803. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-17803 affect?
CVE-2026-17803 affects Google Chrome before 151.0.7922.72, Chromium-based browsers using Save to Drive. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-17803?
Update Chrome to 151.0.7922.72 or later immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Sandbox escape from renderer via crafted PDF, enabling arbitrary code execution on the host system.
Immediate action required
- affected< 151.0.7922.72
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.