Security readout for executives and security teams
Plain-English summary
A malicious webpage could exploit Chrome’s WebGL processing on Android, corrupt memory, and run attacker-controlled code beyond the browser sandbox. A victim must open the crafted page, but no account or prior device access is required. Successful exploitation could compromise sensitive data, device integrity, and availability.
Executive priority
Treat this as an urgent Android browser update because compromise could escape the sandbox and affect confidentiality, integrity, and availability. Expedite organization-wide deployment and verify completion. Escalate exceptions involving privileged or sensitive workflows, while avoiding claims of active attacks unsupported by the supplied evidence.
Technical view
CVE-2026-85050 is a CWE-787 out-of-bounds write in Chrome for Android’s WebGL handling. The supplied record says versions before 152.0.7977.82 permit remote arbitrary code execution outside the sandbox through crafted HTML. CVSS 3.1 is 9.6, reflecting network reachability, low complexity, user interaction, scope change, and high impact.
Likely exposure
Android devices running Chrome earlier than 152.0.7977.82 are the stated exposure. Risk is greatest where users browse untrusted links or sites. The bundle does not establish exposure for desktop Chrome, other Chromium browsers, or Android WebView, so those products require separate vendor confirmation.
Exploitation context
The attack requires a user to open a crafted HTML page; authentication and existing device privileges are not required. The stated outcome is code execution outside Chrome’s sandbox. The CVE is not identified as KEV, and the supplied sources do not establish active exploitation or public exploit availability.
Researcher notes
The bundle contains a scope inconsistency: the description specifies Chrome on Android, while the release reference is titled as a desktop update and the affected array lists 152.0.7977.82. The narrative clearly says versions prior to that release are vulnerable. Confirm final platform and version scope through the cited records before broadening detections.
Mitigation direction
- Update Chrome on Android to version 152.0.7977.82 or later.
- Use managed-browser controls to enforce the corrected version across corporate Android devices.
- Check Google and Chromium guidance for any additional mitigations or revised affected-product information.
- Prioritize devices used for privileged, financial, administrative, or sensitive-data access.
Validation and detection
- Inventory Chrome versions across managed Android devices and identify installations earlier than 152.0.7977.82.
- Confirm upgraded devices report Chrome 152.0.7977.82 or later.
- Verify management policies prevent outdated Chrome installations from remaining in service.
- Monitor the cited Chrome release and Chromium issue pages for updated scope or remediation details.
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-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 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-85050 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_01882797386.htmlCVE reference, Chrome
- https://issues.chromium.org/issues/549350408CVE 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 Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.