Security readout for executives and security teams
Plain-English summary
A malicious website could exploit a memory-handling flaw in Chrome and run attacker-controlled code outside the browser sandbox. The victim must open a crafted HTML page, but no account or prior access is required. Google rates the flaw Critical, making outdated desktop browsers an urgent business risk.
Executive priority
Treat this as an immediate browser-patching priority. The potential outcome is full confidentiality, integrity, and availability impact beyond Chrome's sandbox. Rapidly update and restart Chrome across the fleet, then verify coverage, while recognizing that the supplied sources do not establish active exploitation.
Technical view
CVE-2026-79200 is a use-after-free vulnerability (CWE-416) in Chromium's Aura component. Chrome versions prior to 152.0.7977.65 may permit remote code execution outside the sandbox through crafted HTML. CVSS 3.1 is 9.6: network-accessible, low complexity, no privileges, user interaction required, changed scope, and high impact.
Likely exposure
Exposure exists where Chrome versions earlier than 152.0.7977.65 remain installed or actively used. Internet browsing, links, advertisements, and embedded web content may provide contact with crafted HTML. The supplied evidence does not identify other Chromium-based browsers as affected, so their status should not be assumed.
Exploitation context
Successful exploitation requires a user to load crafted HTML, after which code could execute outside Chrome's sandbox. The supplied record is not in CISA KEV and provides no cited evidence of active exploitation. Public exploit availability and attack prevalence are therefore unknown.
Researcher notes
The record identifies Aura and CWE-416 but supplies no root-cause detail, proof of concept, or exploitation telemetry. The Chromium issue may contain restricted or limited information. Researchers should avoid inferring affected downstream browsers or exploitability conditions beyond crafted HTML, user interaction, low complexity, and sandbox escape stated in the record.
Mitigation direction
- Update desktop Chrome to version 152.0.7977.65 or later.
- Restart Chrome after updating so the corrected version is active.
- Prioritize internet-facing, privileged, and unmanaged user endpoints.
- Enforce browser update policies and address devices that cannot update.
- Consult Google's release guidance for any additional mitigations.
Validation and detection
- Inventory Chrome versions and identify installations earlier than 152.0.7977.65.
- Confirm updated browsers report version 152.0.7977.65 or later after restart.
- Verify enterprise update policies are enabled and successfully applying.
- Recheck offline or unmanaged endpoints when they reconnect.
- Review vendor guidance for revised affected-version or exploitation information.
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-416: 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-79200 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/532921800CVE 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.
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.