Security readout for executives and security teams
Plain-English summary
A malicious webpage could exploit a memory-handling flaw in Chrome’s Dawn graphics component on vulnerable Android devices. Successful exploitation could let an attacker run code outside Chrome’s sandbox, threatening device data, applications, and availability. User interaction is required because the victim must open crafted web content.
Executive priority
Treat this as an urgent endpoint patching issue. Prioritize managed Android fleets with access to sensitive data or corporate applications. The combination of remote delivery, low attack complexity, sandbox escape, and potential code execution supports accelerated remediation, although the supplied sources do not establish active exploitation.
Technical view
CVE-2026-76036 is a heap buffer overflow (CWE-122) in Dawn. The supplied record assigns CVSS 3.1 score 9.6: network-accessible, low complexity, no privileges, user interaction required, changed scope, and high confidentiality, integrity, and availability impact. The description identifies Chrome on Android before 151.0.7922.169 as vulnerable.
Likely exposure
Exposure is highest where Android devices run Chrome versions earlier than 151.0.7922.169 and can browse untrusted content. Internet-facing servers are not the primary target; endpoints are. The supplied affected-version field is internally ambiguous, so vulnerability managers should interpret the narrative version boundary and confirm it against Google guidance.
Exploitation context
The documented attack vector is a crafted HTML page opened by a Chrome user. The bundle does not identify active exploitation, public exploit availability, or indicators of compromise. The CVE is not marked as present in KEV; that does not prove exploitation has never occurred.
Researcher notes
The record attributes the overflow to Dawn and describes code execution outside the sandbox. Source metadata is inconsistent: the title and description specify Android, while the referenced Google post is labeled a desktop stable-channel update. The structured affected entry lists 151.0.7922.169, whereas the description says versions before it are affected. Confirm scope with Google before final reporting.
Mitigation direction
- Update Chrome on Android to 151.0.7922.169 or later.
- Use mobile-device management to enforce Chrome updates across managed Android devices.
- Restrict untrusted browsing on devices that cannot be updated promptly.
- Check Google’s release notice and Chromium issue for revised remediation guidance.
Validation and detection
- Inventory Chrome versions across managed Android devices.
- Confirm every installation is 151.0.7922.169 or later.
- Verify update policies prevent users from indefinitely deferring browser updates.
- Document exceptions for offline, unmanaged, or unsupported Android devices.
- Do not assume compromise from exposure; the supplied sources provide no indicators.
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-122: 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-76036 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/08/stable-channel-update-for-desktop_0826575033.htmlCVE reference, Chrome
- https://issues.chromium.org/issues/540087398CVE 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.
Heap-based Buffer Overflow
Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.