Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to install crafted extension
-
DeliveryVictim installs malicious extension
-
ExploitTrigger use-after-free in Network component
-
ExecutionCorrupt memory to escape sandbox
-
ImpactExecute arbitrary code on 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 the attacker to get a victim to install a crafted, attacker-controlled Chrome extension (CVSS UI:R), typically via social engineering as the description states explicitly. It is NOT remote-unauthenticated against a default configuration: the user must be deceived into installing the malicious extension, which is the primary limiting factor and the reason the vendor rated it 'Low' despite total technical impact. Affected deployments are Chrome desktop versions prior to 155.0.8059.39; updating to that version or later removes the condition. Enterprises that restrict extension installation via policy (allowlisting) substantially reduce exposure. |
| Impact | Signals conflict sharply here. The supplied CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H) yields 9.6 Critical, driven by network vector, no privileges, a scope change (sandbox escape) and total CIA impact. However, the vendor's own Chromium severity rating is explicitly 'Low', and the CISA SSVC decision framework reports Exploitation: none and Automatable: no (Technical Impact: total). The description itself constrains the attack: it requires social engineering AND a crafted Chrome extension to escape the sandbox - a meaningful real-world barrier that the raw 9.6 does not convey. No EPSS score was provided and KEV status is NO, so there is no evidence of widespread or active exploitation. The most likely reading is that this is a high-CVSS-but-moderate-real-risk issue: the theoretical impact (code execution outside the sandbox) is total, but the practical path depends on convincing a user to install an attacker-controlled extension, which is why the vendor rated it Low and SSVC marks it non-automatable. Note the discrepancy explicitly: CVSS 9.6 Critical vs. vendor severity Low and SSVC Exploitation:none - treat the 9.6 as worst-case ceiling, not expected likelihood. Standard priority: patch via the already-available Chrome update, but not an emergency relative to unauthenticated zero-click flaws. |
| Exploit ScenarioDerived | An attacker publishes or sideloads a malicious Chrome extension and uses social engineering (phishing, fake utility, deceptive listing) to persuade a victim to install it. The extension triggers the use-after-free in Chrome's Network component to corrupt memory and execute arbitrary code outside the browser sandbox on the victim's host. No public exploit identified at time of analysis, and no active exploitation is reported (KEV: NO, SSVC Exploitation: none). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 06, 2026
Code execution outside the Chrome sandbox is possible in Google Chrome desktop builds prior to 155.0.8059.39, where a use-after-free in the network component (CVE-2026-106234, CWE-416) can be triggered by a crafted Chrome extension that a remote, unauthenticated attacker convinces a victim to install. The UI:R prerequisite - social engineering the user into installing the extension - is the primary limiting factor, which is why the vendor assigned a Chromium security severity of Low even though the assessed CVSS is 9.6 (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H) and technical impact is rated total in the CISA SSVC framework; the high CVSS and the Low vendor severity are sharply conflicting signals. No public exploit identified at time of analysis (SSVC exploitation: none), and a vendor patch is available.
RemediationAI
Vendor-released patch: Chrome 155.0.8059.39. Update to that version or later via Chrome's built-in updater (chrome://settings/help) or the stable-channel release referenced at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_086471744.html; because the flaw is in shipped browser code, there is no flag or setting that removes the underlying use-after-free. As a compensating control before patching, enterprises can substantially reduce exposure by enforcing extension allowlisting through policy - ExtensionInstallAllowlist/ExtensionInstallBlocklist or ExtensionSettings - and by blocking sideloaded or unpacked extension installation, since the attack path requires the victim to install an attacker-supplied extension; the trade-off is that users lose the ability to add non-approved extensions and administrators must maintain the allowlist. No vendor workaround beyond updating is documented in the available references.
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 defect is a use-after-free (CWE-416) in Chrome's Network component: a heap object is freed while a stale pointer to it remains reachable, and a subsequent dereference can corrupt memory or redirect control flow in the network service process. Chrome runs the network service in a sandboxed process, so an exploit that escapes that boundary - reflected in the assessed vector by the scope-change metric S:C - can execute code with privileges beyond the sandbox, which is why confidentiality, integrity and availability are each rated High despite the Low Chromium severity. The trigger is a crafted Chrome extension rather than ordinary web content, so the attacker must first get attacker-controlled code accepted into the browser's extension context and then deceive the user into installing it; the CVSS vector (AV:N/AC:L/PR:N/UI:R) confirms a remote, unauthenticated adversary but with mandatory user participation, which is precisely why this does not fit the profile of an unauthenticated remote compromise of a default installation. Affected builds are captured by CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* for Chrome releases before 155.0.8059.39.
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
Sources disagree (Low–Critical)AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Delivered over the network via an extension with no attacker privileges but requiring the victim to install it (UI:R); sandbox escape is a scope change (S:C) enabling full code execution (C/I/A:H).
vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.
CVSS VectorVendor: Chrome
Lifecycle Timeline
4DescriptionCVE.org
Use after free in Network in Google Chrome prior to 155.0.8059.39 allowed a remote attacker leveraging social engineering to potentially execute arbitrary code outside the sandbox via a crafted Chrome extension. (Chromium security severity: Low)
Executive ViewAI
Google Chrome desktop versions prior to 155.0.8059.39 contain a critical use-after-free that can allow code execution outside the browser sandbox, putting affected endpoints at risk of full compromise if a user is persuaded to install a crafted extension. Although no public exploit identified at time of analysis, the 9.6 CVSS and sandbox-escape potential make this a high-priority patching event for any organization with Chrome desktop users, especially executives, developers, and administrators. Leadership should care because a successful attack could expose sensitive data, enable lateral movement, and disrupt business operations from an endpoint that is widely deployed across the enterprise.
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-93654
GHSA-hj3x-ccv9-94m4
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB