Sandbox escape via WebAuthn input validation failure
Published Jul 30, 2026 · Updated Jul 30, 2026
Improper input validation in Google Chrome WebAuthn before 151.0.7922.72 allows remote attackers to escape the sandbox via a crafted PDF. Google has not published the specific WebAuthn locus or the incorrect validation operation because the linked Chromium issue remains restricted. Exploitation requires a compromised renderer and user interaction with the PDF, after which code can cross the renderer sandbox boundary.
Summary
What happened
Improper input validation in Google Chrome WebAuthn before 151.0.7922.72 allows remote attackers to escape the sandbox via a crafted PDF. Google has not published the specific WebAuthn locus or the incorrect validation operation because the linked Chromium issue remains restricted. Exploitation requires a compromised renderer and user interaction with the PDF, after which code can cross the renderer sandbox boundary.
The record
- CVE
- CVE-2026-17990
- Published
- Jul 30, 2026
- Updated
- Jul 30, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-20, T1068
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 30, 2026CVE publishedPublication date reported by the CVE source.
- Jul 30, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=151.0.7922.72 <151.0.7922.72
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo