Skip to content
major vulnerability· requires attention

Affects widely deployed Google Chrome; sandbox escape via crafted PDF can lead to host compromise and widespread impact across organizations.

Web

CVE-2026-17990

9.6
Critical
EPSS 0.22%Patch availableJul 31, 2026

Chrome WebAuthn input validation allows sandbox escape via crafted PDF (pre-151.0.7922.72)

common questions

Is CVE-2026-17990 being exploited?

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

How severe is CVE-2026-17990?

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

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

What does CVE-2026-17990 affect?

CVE-2026-17990 affects Google Chrome < 151.0.7922.72, Chromium-based browsers (potentially). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-17990?

Update Chrome to 151.0.7922.72+ and 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 < 151.0.7922.72Chromium-based browsers (potentially)
impact

Sandbox escape from a compromised renderer via crafted PDF, enabling code execution on host, persistence, and data access.

action required

Immediate action required

affected versions
Google Chrome
  • 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.

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