Security readout for executives and security teams
Plain-English summary
Google Chrome versions before 151.0.7922.72 contain a WebAuthn input-validation flaw. An attacker who has already compromised Chrome’s renderer could use a crafted PDF to potentially escape the browser sandbox, increasing control over the affected system.
Executive priority
Treat this as an urgent browser update, particularly for high-risk users, but not as evidence of an active emergency. The high CVSS reflects sandbox-escape impact, while the required renderer compromise and Chromium’s Low rating materially reduce standalone likelihood.
Technical view
CVE-2026-17990 is a CWE-20 input-validation weakness in Chrome’s WebAuthn implementation. Exploitation requires prior renderer compromise and user interaction with a crafted PDF. The supplied CVSS is 9.6, although Chromium rates the issue Low, creating a material severity discrepancy.
Likely exposure
Exposure is limited to Google Chrome installations earlier than 151.0.7922.72. Practical exploitation requires a compromised renderer plus a crafted PDF, so this is primarily a vulnerability-chain risk rather than a standalone initial-entry issue.
Exploitation context
The source bundle does not establish active exploitation, and the CVE is not listed as KEV. No public exploit evidence is provided. The vulnerability could strengthen a multi-stage browser attack by allowing an existing renderer compromise to potentially cross the sandbox boundary.
Researcher notes
Important evidence gaps remain: the bundle provides no exploit details, telemetry, or confirmation of attacks. Analysts should model this as a chain component requiring renderer compromise. The affected-version entry lists 151.0.7922.72, but the description identifies versions before that release as vulnerable.
Mitigation direction
- Update Google Chrome to version 151.0.7922.72 or later.
- Prioritize endpoints handling untrusted PDFs or exposed to higher browser-attack risk.
- Review Google and Chromium guidance for any additional mitigations or revised release information.
Validation and detection
- Inventory Chrome versions and identify installations earlier than 151.0.7922.72.
- Confirm updated endpoints report version 151.0.7922.72 or later.
- Verify browser management systems successfully enforced the update across managed devices.
- Monitor the Chromium issue and Chrome release notice for updated exploitation information.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-20: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-17990 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H2.86CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.6CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.htmlCVE reference, Chrome
- https://issues.chromium.org/issues/520018012CVE reference, Chrome
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Input Validation
Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.