Security readout for executives and security teams
Plain-English summary
A malicious webpage could let an attacker who already controls Chrome’s rendering process break out of its security sandbox on Android. A successful chain could expose sensitive data, alter device activity, or disrupt availability. The issue affects Chrome versions before 151.0.7922.72 and requires user interaction.
Executive priority
Treat this as an urgent Android browser update because successful exploitation could cross Chrome’s sandbox boundary with high confidentiality, integrity, and availability impact. Prioritize rapid fleet inventory and patch verification, while avoiding claims of an active campaign because the supplied evidence does not support one.
Technical view
CVE-2026-17713 is an input-validation weakness in Chrome’s Android Accessibility component. A remote attacker with a compromised renderer could use crafted HTML to potentially escape the sandbox. The supplied CVSS 3.1 score is 9.6, while Chromium rates the vulnerability High. The weakness is classified as CWE-20.
Likely exposure
Android devices running Chrome earlier than 151.0.7922.72 are potentially exposed, particularly where users browse untrusted content. The source bundle’s affected-version field conflicts with its description, so inventory decisions should follow the explicit “prior to 151.0.7922.72” wording and confirm against current Google guidance.
Exploitation context
Exploitation requires a crafted webpage, user interaction, and prior compromise of Chrome’s renderer process, indicating a chained attack rather than a standalone sandbox escape. The supplied record is not in KEV, and no cited evidence establishes active exploitation. Public exploit availability is not established by the source bundle.
Researcher notes
The vulnerability concerns insufficient validation of untrusted input in Accessibility and requires renderer compromise before sandbox escape. The source bundle does not disclose root-cause details, proof-of-concept availability, or confirmed exploitation. Its structured affected-version entry lists 151.0.7922.72, conflicting with the description that versions before that release are affected.
Mitigation direction
- Update Chrome on Android to version 151.0.7922.72 or later.
- Prioritize managed Android devices that access untrusted or externally supplied links.
- Confirm the approved release and any additional precautions in current Google guidance.
- Restrict outdated devices from sensitive workflows until remediation is verified.
Validation and detection
- Inventory Chrome versions across managed Android devices.
- Flag installations earlier than 151.0.7922.72 for remediation.
- Verify updated devices report version 151.0.7922.72 or later.
- Review endpoint telemetry for persistent outdated installations or failed updates.
- Confirm browser update enforcement through mobile-device management controls.
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-17713 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/520572766CVE 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.