Security readout for executives and security teams
Plain-English summary
A malicious website could exploit a flaw in Chrome’s Dawn graphics component and potentially run code outside Chrome’s security sandbox. Successful exploitation requires a user to open a crafted HTML page, but needs no account or prior system access. The stated fixed version is Chrome 152.0.7977.65.
Executive priority
Treat this as an urgent browser patching event. Prioritize high-value users, administrators, developers, and systems handling sensitive information. Require rapid deployment and measurable version compliance, while avoiding claims of an active campaign because the supplied evidence does not support one.
Technical view
CVE-2026-79111 is improper input validation (CWE-20) in Dawn. Chrome versions before 152.0.7977.65 may permit sandbox escape and arbitrary code execution through crafted HTML. CVSS 3.1 is 9.6: network-accessible, low complexity, no privileges, user interaction required, changed scope, and high confidentiality, integrity, and availability impact.
Likely exposure
Endpoints running Chrome versions earlier than 152.0.7977.65 are potentially exposed, especially where users browse untrusted sites. Internet-facing servers are not the primary exposure described. Inventory gaps, delayed browser restarts, unmanaged devices, and failed automatic updates may leave vulnerable installations present.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not listed as KEV in the bundle. Exploitation requires a victim to visit a crafted HTML page. The low-complexity, no-privilege path and potential sandbox escape make exploitation plausible, but observed attacks must not be assumed without additional evidence.
Researcher notes
The published description identifies Dawn input validation but provides no root-cause, object-lifetime, or affected-code-path detail. The CVSS scope change reflects execution outside the browser sandbox. Researchers should distinguish the fixed release from affected releases: the narrative says versions before 152.0.7977.65 are vulnerable. No exploitability demonstration is included.
Mitigation direction
- Update Chrome to version 152.0.7977.65 or later.
- Require users to restart Chrome so the updated version becomes active.
- Accelerate deployment through enterprise browser-management policies.
- Restrict untrusted browsing on systems that cannot be updated promptly.
- Monitor Google and Chromium guidance for revised remediation information.
Validation and detection
- Inventory installed and actively running Chrome versions across managed endpoints.
- Confirm every Chrome instance reports version 152.0.7977.65 or later.
- Verify updated browsers were restarted after installation.
- Investigate endpoints where automatic updates failed or management telemetry is missing.
- Review security telemetry for suspicious browser-originated activity without assuming CVE attribution.
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-20: 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-79111 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_0256176589.htmlCVE reference, Chrome
- https://issues.chromium.org/issues/525683797CVE 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.
Improper Input Validation
Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.