CVE-2026-17710: Inappropriate implementation in MHTML in Google Chrome on Mac prior to 151.0.7922.72 allowed a remote attac...
Inappropriate implementation in MHTML in Google Chrome on Mac prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
Security readout for executives and security teams
Plain-English summary
A Chrome for Mac flaw could let an attacker escape the browser sandbox after first compromising Chrome’s renderer through a crafted web page. A successful chain could expose or alter data and affect the Mac beyond the compromised browser tab. The supplied CVSS score is 9.6, although Chromium classifies the issue as High severity.
Executive priority
Treat this as an urgent Mac browser update because successful exploitation could cross Chrome’s security boundary with broad system impact. Accelerate deployment and verify coverage, while avoiding claims of an ongoing campaign: the supplied evidence does not show active exploitation. Focus first on privileged users, sensitive-data handlers, and heavily exposed browsing environments.
Technical view
CVE-2026-17710 is an inappropriate MHTML implementation in Chrome for Mac before 151.0.7922.72. A remote attacker who already controls the renderer could potentially escape the sandbox using crafted HTML. The supplied vector indicates network delivery, low complexity, user interaction, changed scope, and high confidentiality, integrity, and availability impact. The weakness is mapped to CWE-693.
Likely exposure
Mac systems running Google Chrome versions earlier than 151.0.7922.72 are the stated exposure. Risk is greatest where users browse untrusted content or renderer compromise is otherwise possible. The bundle does not establish exposure for Windows, Linux, other Chromium browsers, or Chrome 151.0.7922.72 and later.
Exploitation context
Exploitation is not described as a standalone sandbox escape: the attacker must first compromise the renderer and induce interaction with crafted HTML. The CVE is not listed as KEV in the supplied bundle, and no cited evidence establishes active exploitation. Public exploit availability is not established by the provided sources.
Researcher notes
The flaw concerns MHTML security-boundary enforcement and requires a prior renderer compromise, suggesting use within an exploit chain. The supplied affected entry lists 151.0.7922.72, while the description says versions prior to that release; assessment should follow the description and confirm against vendor records. The Chromium issue may restrict technical details, and the bundle provides no root-cause specifics.
Mitigation direction
Update Chrome on Mac to 151.0.7922.72 or later through approved management channels.
Prioritize Macs that browse untrusted sites or handle sensitive data.
Check Google and Chromium guidance for any additional mitigations or release changes.
Restrict unsupported or unmanaged Chrome installations until their versions can be verified.
Validation and detection
Inventory Chrome versions across managed Mac endpoints.
Confirm every Mac runs Chrome 151.0.7922.72 or later.
Verify browser management reports successful update deployment and restart completion.
Review endpoint telemetry for unexpected activity following renderer or browser crashes.
Recheck vendor advisories for revised affected-version or exploitation information.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · low confidence lookup
CWE-693: 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.
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.
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.
1CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-693 · source CWE mapping
Protection Mechanism Failure
Protection Mechanism Failure represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.