Security readout for executives and security teams
Plain-English summary
A race-condition flaw in Chrome’s Downloads handling on macOS could let an attacker escape Chrome’s security sandbox after first compromising a browser renderer. Successful exploitation could expose sensitive data, alter systems, or disrupt operations. The crafted page requires user interaction, but the potential impact is severe.
Executive priority
Treat this as an urgent browser-update requirement. The prerequisite renderer compromise reduces standalone exploitability, but a successful chain could escape browser isolation with high confidentiality, integrity, and availability impact. Expedite deployment and verify coverage rather than relying only on automatic-update policy.
Technical view
CVE-2026-17711 is a CWE-362 race condition affecting Google Chrome on Mac before 151.0.7922.72. A remote attacker with an already-compromised renderer could potentially trigger a sandbox escape through crafted HTML. Chromium rates the issue High; the supplied CVSS 3.1 score is 9.6 Critical.
Likely exposure
Mac endpoints running Chrome versions earlier than 151.0.7922.72 are potentially exposed. Risk is greatest where users browse untrusted content or endpoints lack rapid browser updating. The supplied structured version entry is ambiguous, but the CVE description identifies versions prior to 151.0.7922.72 as vulnerable.
Exploitation context
The public bundle does not establish active exploitation, and the CVE is not listed as KEV. Exploitation requires user interaction and prior renderer compromise, suggesting this flaw would likely form part of a vulnerability chain rather than serve as a standalone initial compromise.
Researcher notes
The disclosed weakness is a Downloads race condition categorized as CWE-362. Public evidence provides no detailed mechanics, exploit proof, or confirmed exploitation. Defensive validation should focus on version state, update completion, and suspicious browser behavior; safely reproducing the race is not supported by the supplied evidence.
Mitigation direction
- Update Chrome on macOS to 151.0.7922.72 or later.
- Prioritize managed Macs handling sensitive data or browsing untrusted websites.
- Enforce automatic browser updates and investigate devices that cannot update.
- Review current Google guidance for any additional mitigations or revised release information.
Validation and detection
- Inventory Chrome versions across all managed macOS endpoints.
- Confirm no Mac remains on a version earlier than 151.0.7922.72.
- Verify updated browsers were restarted and report the expected version.
- Monitor endpoint telemetry for unusual Chrome child-process or sandbox-related activity.
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-362: 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-17711 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/519996040CVE 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.
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.