Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
ExploitTrigger use-after-free in WebAppInstalls
-
ExecutionReclaim freed object via heap grooming
-
ImpactExecute arbitrary code in renderer sandbox
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 victim to use an affected Chrome build (prior to 156.0.8078.47) and to navigate to attacker-controlled content - the crafted HTML page that triggers the use-after-free in the WebAppInstalls component (UI:R). No authentication or special privileges are needed (PR:N), and default configurations are affected since WebAppInstalls is a built-in Chrome capability. The principal limiting factors are: (1) mandatory user interaction (the victim must open the malicious page), and (2) sandbox containment - the resulting arbitrary code execution is explicitly confined to the renderer sandbox, so full host compromise additionally requires a separate sandbox-escape vulnerability not covered by this CVE. |
| Impact | Signals conflict sharply here. The NVD CVSS 3.1 vector (8.8, AV:N/AC:L/PR:N/UI:R/C:H/I:H/A:H) scores this as High, implying remote code execution with low complexity and no privileges - but the description explicitly scopes code execution to 'inside the sandbox,' and Google/Chromium rated the security severity as Low. These two facts are the key tension: an 8.8 raw score overstates real-world impact because a renderer-sandbox-contained UAF does not by itself yield host compromise; an attacker would additionally need a separate sandbox-escape bug to reach the underlying OS. No EPSS score, no CISA KEV listing, and no public POC are present in the provided data, so there is no evidence of exploitation probability or active use - this appears to be no public exploit identified at time of analysis. The UI:R requirement (victim must open a crafted page) further lowers practical risk versus a drive-by with zero interaction. Net assessment: patch on the normal Chrome update cadence; this is a genuine memory-corruption bug in a ubiquitous product but is NOT a drop-everything emergency given sandbox containment, vendor's Low rating, and absence of exploitation signals. Note the CVSS-vs-vendor-severity divergence should be reconciled against Google's advisory rather than treating 8.8 as the operative priority. |
| Exploit ScenarioDerived | An attacker hosts or compromises a web page containing crafted HTML/JavaScript that triggers the use-after-free in Chrome's WebAppInstalls component; a victim running a vulnerable version (prior to 156.0.8078.47) visits the page and the freed object is reused to achieve arbitrary code execution within the renderer sandbox. No authentication is required (PR:N) but user interaction is (UI:R), and the gained code execution remains confined to the sandbox absent a chained escape. No public exploit code was identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Use-after-free in Google Chrome's WebAppInstalls component, affecting versions prior to 156.0.8078.47, lets an unauthenticated remote attacker execute arbitrary code inside the browser sandbox when a victim opens a crafted HTML page; the CVSS vector requires user interaction (UI:R) and does not require privileges (PR:N). The 8.8 CVSS rating contrasts with Google's Low Chromium severity because the code execution is confined to the renderer sandbox and full host compromise would require a separate sandbox escape. No public exploit was identified at time of analysis, and Google has released Chrome 156.0.8078.47 as the fixed build.
RemediationAI
Upgrade Google Chrome to 156.0.8078.47 or later from the stable channel (https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html) and restart the browser; managed fleets should force the update and verify the reported version. If immediate patching is not possible, reduce exposure by restricting users to trusted sites or routing untrusted web content through remote browser isolation, and block outdated Chrome builds from accessing sensitive internal web applications-trade-offs include reduced browsing functionality, added latency and operational overhead, and potential compatibility issues. No specific feature-disable workaround is documented in the supplied references, so updating is the primary remediation; the Chromium issue tracker entry is https://issues.chromium.org/issues/533135911.
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 flaw is CWE-416, a use-after-free in Chrome's WebAppInstalls code path, which handles web application and PWA installation flows. A crafted HTML page can cause an object to be freed while still referenced, producing memory corruption that the attacker can steer into arbitrary code execution in the renderer. The CVSS:3.1 vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H describes network-reachable, low-complexity exploitation with no privileges but mandatory victim interaction; scope is unchanged and impact is high within the sandbox. The input did not provide CPE strings, but EUVD identifies Chrome builds before 156.0.8078.47 as affected, and Google's advisory is the desktop stable-channel update. Sandbox containment is the key reason Chromium severity is Low despite the high CVSS base score, and no public exploit code was identified in the supplied intelligence.
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:U/C:H/I:H/A:H
Remotely reachable via a crafted page (AV:N/AC:L/PR:N) requiring the victim to open it (UI:R); code execution is sandbox-contained (S:U) but still yields high impact to browser-held data, so C/I/A:H.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Use after free in WebAppInstalls in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Low)
Executive ViewAI
Google Chrome builds prior to 156.0.8078.47 carry a use-after-free defect in the WebAppInstalls component that lets a crafted web page run attacker-controlled code inside the browser's renderer sandbox, so any employee who browses untrusted or malformed content is a potential entry point. Google rates the underlying Chromium issue Low because the sandbox contains the code execution, but the 8.8 CVSS score and the simple user-interaction trigger mean it is a credible first stage in a multi-step intrusion rather than a theoretical flaw. Leadership should view this as a fleet-wide browser hygiene obligation affecting the entire workforce, with remediation cost that is low but highly time-sensitive.
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-105719
GHSA-r9rj-9v9r-pp9h
NVD
CVE.org
EPSS
Exploit-DB