Analyst readout for executives and security teams
Plain-English summary
CVE-2026-9889 is a Chrome on Android memory-safety flaw in Dawn. A malicious webpage could potentially escape Chrome’s sandbox, which raises the risk from browser compromise to broader device impact. The available sources do not report active exploitation.
Executive priority
Treat this as a high-priority mobile browser update. The potential sandbox escape impact is serious, but public evidence provided here does not show active exploitation or broad attack automation.
Technical view
The CVE describes out-of-bounds read and write behavior in Dawn in Google Chrome on Android prior to 148.0.7778.216. Attack vector is network, requires user interaction, and has high complexity. Scope is changed with high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely on Android devices running Google Chrome versions before 148.0.7778.216. The source bundle does not identify other affected Chromium-based products or platforms.
Exploitation context
Sources say exploitation could occur through a crafted HTML page. CISA KEV status is false in the bundle, and no cited source states active exploitation. The Chromium issue may have limited details.
Researcher notes
Key gaps remain: the public bundle does not provide root-cause detail, proof of exploitation, or a standalone vendor advisory for Android beyond the CVE description and Chrome references. Avoid assuming impact beyond Chrome on Android.
Mitigation direction
- Update Google Chrome on Android to 148.0.7778.216 or later where available.
- Use mobile device management to confirm Chrome update compliance.
- Prioritize updates for executives, administrators, and high-risk mobile users.
- Monitor Google Chrome release notes and the Chromium issue for additional guidance.
Validation and detection
- Inventory Android devices and record installed Chrome versions.
- Flag Chrome versions earlier than 148.0.7778.216 as exposed.
- Confirm updates through managed device reporting or user device checks.
- Review mobile browsing telemetry for unusual Chrome crashes if available.
Public sources used
Based on public source material and reviewed before publication.
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-125: 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 lookupCWE-787: 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-9889 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
- High
- CVSS
- 8.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/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:H/PR:N/UI:R/S:C/C:H/I:H/A:H 1.6 6 CISA-ADP Vulnerability scoring details
Base CVSS 3.1 score
8.3 HighVector: CVSS:3.1/AV:N/AC:H/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 reserved CVE Program
The CVE ID was reserved by the assigning CNA.
- CVE published CVE Program
The CVE record was published.
- CVE updated CVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 source CVE List V5
- https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_0877304591.html CVE reference, Chrome
- https://issues.chromium.org/issues/511727159 CVE 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.
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.