Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
DeliveryTrigger use-after-free in Chrome Tabs
-
ExploitCorrupt freed heap object
-
ExecutionExecute code and escape sandbox
-
ImpactRun arbitrary code on macOS host
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Memory lifecycle management
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a macOS user running Google Chrome prior to 155.0.8059.39 to load attacker-controlled web content - the 'crafted HTML page' named in the description is the concrete trigger, exercising the use-after-free in the Chrome Tabs component. The chief limiting factor is required user interaction (CVSS UI:R): the victim must navigate to or open the malicious page; there is no zero-click vector indicated. No authentication is required (PR:N), and no non-default configuration is needed - default Chrome on affected macOS builds is vulnerable. Exploitation is platform-scoped to Mac per the advisory; achieving reliable code execution outside the sandbox additionally depends on successful heap grooming of the freed object. |
| Impact | This is a genuine high-priority issue, not a high-CVSS-but-low-real-risk case. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, score 9.6) describes a network-reachable, low-complexity, unauthenticated flaw whose only gating factor is user interaction (UI:R), and the scope change (S:C) reflects that a successful attack escapes the Chrome renderer sandbox - the most impactful class of browser bug. The use-after-free (CWE-416) combined with the vendor-stated 'potentially execute arbitrary code outside the sandbox' means full host compromise is plausible. However, several exploitation signals are MISSING from the input: there is no EPSS probability, no CISA KEV listing, and no POC indicator provided, so exploitation status is 'no public exploit identified at time of analysis.' That absence should not be read as low risk - browser sandbox-escape UAFs are historically weaponized quickly, but as of this analysis there is no evidence of active exploitation. The primary limiting factor versus a 'drive-by with zero interaction' worst case is UI:R: a victim must open a crafted HTML page. Net: patch urgently given the impact and trivial attack complexity, while treating 'active exploitation' as unconfirmed rather than assumed. |
| Exploit ScenarioDerived | An attacker hosts a malicious HTML page (or injects crafted markup into a compromised/advertising-served page) that triggers the use-after-free in Chrome's Tabs component when a macOS user visits it. By grooming the heap around the freed object, the attacker achieves memory corruption that leads to arbitrary code execution outside the renderer sandbox. No public proof-of-concept is indicated in the provided data, and exploitation requires the victim to load the page (UI:R). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 06, 2026
A use-after-free in the Chrome Tabs component of Google Chrome on macOS allows a remote attacker to potentially execute arbitrary code outside the sandbox when a victim loads a crafted HTML page, affecting all builds prior to 155.0.8059.39. Exploitation is unauthenticated (CVSS PR:N) but requires user interaction (UI:R) - the victim must navigate to or open attacker-controlled web content, with no zero-click vector indicated, and reliable code execution additionally depends on successful heap grooming of the freed object. The issue is assessed as a genuine high-priority problem rather than a high-CVSS-but-low-real-risk case (CVSS 9.6, scope-changed), and no public exploit was identified at time of analysis; a vendor patch is available in Chrome 155.0.8059.39.
RemediationAI
Vendor-released patch: Google Chrome 155.0.8059.39 for macOS. Upgrade to 155.0.8059.39 or later - Chrome's built-in updater normally handles this, but managed fleets should force the update via enterprise policy (for example, relaunch-notification and auto-update policies) since Chrome applies updates only on browser restart, leaving long-running sessions exposed. Verify the installed build from chrome://version and confirm the platform is macOS, as the advisory scopes the flaw to Mac. No vendor-published workaround exists for the underlying use-after-free in the Tabs component, so compensating controls are exposure-limiting rather than fixes: restrict browsing to trusted origins or isolate untrusted browsing in a separate VM/container or distinct OS user profile (trade-off: added friction and management overhead, and users may bypass it), and reduce the window of exposure by enforcing scheduled browser restarts (trade-off: interrupts active sessions and may lose unsaved tab state). Keep macOS hardened and current to raise the cost of post-exploitation if the UAF is triggered, and monitor Chrome release notes for any follow-up fixes to this issue. Reference advisory: https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_086471744.html; engineering issue: https://issues.chromium.org/issues/555932520.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-416, use-after-free, in the Chrome Tabs component - the browser-process UI layer that manages tab lifecycles, tab switching, and associated per-tab state. Because the Tabs component lives in Chrome's browser process rather than the renderer, a successful use-after-free there is inherently outside the renderer sandbox, which is consistent with the CVSS scope-changed (S:C) rating and the advisory's statement that code execution occurs outside the sandbox. The attack surface is a crafted HTML page: the attacker must induce the victim to load attacker-controlled content that triggers the faulty free/reuse sequence during tab manipulation. The input CPE (cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*) is a wildcard covering the Google Chrome product line, and the EUVD entry scopes the fixed build at 155.0.8059.39; the advisory explicitly limits the affected platform to Mac. Tags accompanying the record (RCE, memory corruption, use-after-free, denial of service) are consistent with the UAF class, where the same dangling object can also be leveraged for a crash-driven DoS.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Remote crafted web page (AV:N, AC:L, PR:N) requires the victim to open it (UI:R); sandbox escape changes scope (S:C) and arbitrary code execution yields full C/I/A impact.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
4DescriptionCVE.org
Use after free in Chrome Tabs in Google Chrome on on Mac prior to 155.0.8059.39 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)
Executive ViewAI
Google Chrome on macOS is affected by a critical memory-safety flaw in the Tabs component that could allow a remote attacker to run code outside the browser sandbox on any employee machine running a build prior to 155.0.8059.39. Because exploitation only requires a user to open a crafted web page - with no additional credentials - the population at risk is effectively every macOS user in the organization, including executives and privileged administrators. While no public exploit has been identified at time of analysis, the combination of a critical CVSS rating, sandbox escape potential, and Chrome's ubiquity makes this a patch-within-days priority rather than a routine update.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Use-after-free vulnerabilities occur when a program continues to access memory through a pointer after that memory has been deallocated.
Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
EUVD-2026-93823
GHSA-fv87-fv73-32rj
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB