Security readout for executives and security teams
Plain-English summary
A critical memory-safety flaw in Chrome’s Shared Tab Groups on Android could let an attacker take control after persuading a user to open a malicious webpage. Successful exploitation could compromise sensitive data, alter information, or disrupt the device, with code executing beyond Chrome’s sandbox protections.
Executive priority
Treat this as an urgent Android browser update because successful exploitation could escape Chrome’s sandbox and materially compromise confidentiality, integrity, and availability. Prioritize internet-facing user devices and high-value personnel, while recognizing that the supplied evidence does not establish active exploitation.
Technical view
CVE-2026-84353 is a use-after-free vulnerability (CWE-416) in Chrome Shared Tab Groups on Android before 152.0.7977.75. A remote, unauthenticated attacker can use crafted HTML and social engineering to trigger arbitrary code execution outside the sandbox. The supplied CVSS 3.1 score is 9.6, with user interaction required.
Likely exposure
Android devices running Chrome versions earlier than 152.0.7977.75 are potentially exposed, particularly where users browse untrusted links. The bundle’s affected-version field lists 152.0.7977.75 while its description says versions before that release; confirm applicability against current Google guidance.
Exploitation context
Exploitation requires a user to interact with attacker-controlled HTML through social engineering. The bundle does not identify CVE-2026-84353 as a CISA KEV entry and provides no evidence of active exploitation. Public exploit availability is not established by the supplied sources.
Researcher notes
The record describes an Android Shared Tab Groups use-after-free with sandbox escape, but links to a desktop stable-channel post and contains an ambiguous affected-version entry. Chromium’s issue may restrict technical details. Validate platform scope and version boundaries before making definitive exposure claims; no root cause or exploit reliability details are supplied.
Mitigation direction
- Update Chrome on Android to version 152.0.7977.75 or later.
- Enable managed automatic browser updates where available.
- Restrict access to untrusted links until affected devices are updated.
- Check Google’s current release guidance for any additional mitigations or corrected platform details.
Validation and detection
- Inventory Chrome versions across managed Android devices.
- Confirm each Android installation reports version 152.0.7977.75 or later.
- Verify automatic updates are enabled and successfully completing.
- Review browser security telemetry for suspicious crashes or activity involving untrusted webpages.
- Reconcile the Android description with the desktop-titled Google release reference.
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-416: 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-84353 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/09/stable-channel-update-for-desktop.htmlCVE reference, Chrome
- https://issues.chromium.org/issues/522307103CVE 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.
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.