Security readout for executives and security teams
Plain-English summary
A malicious app already installed on an Android device could abuse Chrome Custom Tabs to cross website security boundaries. The prerequisite of local, co-installed software limits broad remote risk. The bundle’s critical rating and CVSS 9.8 conflict with Chromium’s Low severity assessment, so urgency should reflect actual Android exposure.
Executive priority
Use expedited routine patching for managed Android fleets, with higher priority where users can install untrusted apps. Immediate crisis response is not supported by the supplied evidence because exploitation is unconfirmed and requires a co-installed app. Track vendor clarification because the critical CVSS data conflicts materially with Chromium’s Low rating.
Technical view
CVE-2026-79152 is an incorrect-authorization flaw in Chrome CustomTabs on Android before 152.0.7977.65. A local attacker operating through a co-installed app could bypass web origin policy. The supplied network-based CVSS vector conflicts with the stated local attack path and should not be used alone for prioritization.
Likely exposure
Exposure is limited to Android devices running Chrome versions before 152.0.7977.65 where an attacker-controlled or compromised app is also installed. Desktop exposure is not established by the supplied description. The affected-version entry is ambiguous because it lists 152.0.7977.65 while the description identifies earlier versions as vulnerable.
Exploitation context
The bundle does not report active exploitation, and the CVE is not listed as KEV. Successful abuse reportedly requires a co-installed app and local attacker context. No evidence supplied supports unauthenticated remote exploitation, despite the contradictory CVSS vector.
Researcher notes
Key evidence is internally inconsistent: CVSS 9.8 specifies network access without privileges or interaction, while the description requires a local attacker and co-installed app. The reference title concerns a desktop stable update although the CVE describes Android CustomTabs. Treat platform, scoring, and affected-version metadata cautiously pending authoritative clarification.
Mitigation direction
- Update Android Chrome to 152.0.7977.65 or later through approved deployment channels.
- Prioritize managed devices that permit untrusted or sideloaded applications.
- Review vendor guidance and the Chromium issue for revised affected-version information.
- Restrict installation of unapproved Android applications where operationally appropriate.
Validation and detection
- Inventory Android Chrome versions and identify installations earlier than 152.0.7977.65.
- Confirm updated devices report version 152.0.7977.65 or later.
- Review mobile-management telemetry for unapproved or sideloaded applications.
- Check subsequent vendor notices for clarification of the conflicting severity and attack vector.
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-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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 lookupCVE-2026-79152 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.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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:N/S:U/C:H/I:H/A:H3.95.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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/08/stable-channel-update-for-desktop_0256176589.htmlCVE reference, Chrome
- https://issues.chromium.org/issues/533083384CVE 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.
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.