Skip to main content

Google Chrome CVE-2026-113321

| EUVDEUVD-2026-105550 HIGH
Use After Free (CWE-416)
2026-10-20 chrome-cve-admin@google.com GHSA-pjpp-x4p6-8mj4
8.8
CVSS 3.1 · Vendor: google
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Lure victim to crafted HTML page
  2. Delivery
    Deliver malicious script targeting Extensions
  3. Exploit
    Trigger use-after-free (CWE-416)
  4. Execution
    Reclaim freed memory with controlled data
  5. Impact
    Execute arbitrary code within 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 open a crafted HTML page in a vulnerable Chrome build (prior to 156.0.8078.47), so active user interaction (UI:R) is mandatory - there is no server-side or passive trigger. The flaw resides in the Extensions component and is reachable from web content, needing no authentication or privileges (PR:N). The key limiting factor is that resulting code execution is explicitly confined to the renderer sandbox (Scope:Unchanged); meaningful host compromise additionally requires chaining a separate sandbox-escape vulnerability. Applying the already-available update to 156.0.8078.47 or later fully remediates the condition.

Impact

Signals are mixed. The NVD CVSS 3.1 base score is 8.8 (High) with AV:N/AC:L/PR:N/UI:R, indicating a low-complexity, unauthenticated, network-reachable flaw requiring only that a victim open a page - yet Google's own Chromium security team rated this 'Medium', and the description explicitly states code execution occurs 'inside the sandbox' (Scope:Unchanged). That sandbox confinement is the decisive mitigating factor: without a chained sandbox-escape vulnerability, a successful UAF exploit does not directly yield host/system compromise, so the effective real-world impact is lower than the 8.8 suggests. No EPSS score was provided in the input, there is no CISA KEV listing, and no public exploit code was referenced, so exploitation status is: no public exploit identified at time of analysis. SSVC-style read: exploitation=none observed, automatable=no (requires user interaction via crafted page), technical impact=partial (confined to renderer sandbox). Net: this is a legitimate patch-now item because Chrome is ubiquitous and the fix is already shipped, but it is not an emergency on its own - it is a sandboxed-RCE primitive, not confirmed end-to-end system compromise. Conflict to note explicitly: vendor severity 'Medium' vs NVD 'High (8.8)' - the gap is explained by sandbox containment, which CVSS base metrics do not credit.

Exploit ScenarioDerived

An attacker hosts a malicious or compromised web page containing crafted HTML/JavaScript that abuses the Extensions component to trigger a use-after-free. A victim running Chrome prior to 156.0.8078.47 visits the page (the required user interaction), the freed object is reclaimed with attacker-controlled data, and arbitrary code executes within the renderer sandbox. No public proof-of-concept exploit was identified at the time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 21, 2026

Use-after-free in Google Chrome's Extensions component (versions prior to 156.0.8078.47) lets a remote attacker who convinces a victim to open a crafted HTML page corrupt memory and execute arbitrary code inside the renderer sandbox, and can additionally crash the browser. Exploitation is not passive: it requires the target to load attacker-controlled web content, and because the CVSS scope is Unchanged, code execution stays confined to the sandbox - full host compromise would require chaining a separate sandbox escape. No public exploit code or confirmed active exploitation was identified at time of analysis, though Chrome renderer memory-corruption bugs are historically attractive to exploit developers; the risk picture is mixed, with Chromium's own severity rating of Medium sitting well below the 8.8 CVSS score derived from the high confidentiality and integrity impact.

RemediationAI

Vendor-released patch: upgrade Google Chrome to 156.0.8078.47 or later - this fully remediates the condition per the vendor advisory at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html. Chrome's auto-updater normally delivers this, but verify the on-disk version (chrome://settings/help) because staged rollouts can leave fleets behind; also confirm any Chromium-derived browsers and embedded/headless Chrome instances (automation, Electron-style wrappers, testing grids) have picked up a build containing the upstream fix. Where immediate upgrade is impossible, reduce exposure by restricting the Extensions surface with enterprise policy - an ExtensionSettings blocklist/allowlist limiting installation to vetted extensions, and disabling developer mode and untrusted sideloading - though the trade-off is administrative overhead and potential breakage of legitimate internal tooling, and it does not remove the underlying bug. Enforce Site Isolation (on by default, keep it that way) and avoid weakening the renderer sandbox, since sandbox confinement is the main reason this bug does not translate directly into host compromise; note that any such configuration changes are compensations, not fixes. Because exploitation requires the user to open a crafted page, web-content filtering and phishing-resistant browsing hygiene lower practical risk but should not substitute for patching.

Affected VersionsENISA

Chrome 156.0.8078.47 <156.0.8078.47

Affected Packages

euvd chrome fix: 156.0.8078.47

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: an object in the Extensions subsystem is freed while a live reference to it remains, so subsequent access dereferences stale memory. In Chromium, extensions are deeply intertwined with the renderer and browser processes - extension APIs, content scripts, and message-passing plumbing all allocate and release objects under complex lifetimes - and a dangling reference reachable from web content gives an attacker a classic heap-shaping primitive (reclaiming the freed allocation with controlled data) that can redirect control flow. The affected component per Chromium's own classification is Extensions, and the vulnerability is triggered by a crafted HTML page, meaning the attacker only needs the victim to navigate to hostile or compromised content rather than any local foothold. Per the assessed vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), the attack is network-delivered, low complexity, unauthenticated, and requires user interaction; scope is Unchanged, so the resulting arbitrary code execution is constrained to the renderer sandbox and does not by itself grant host-level privileges. The accompanying tags (RCE, Denial of Service, Memory Corruption) reflect the dual outcome of use-after-free bugs - reliable code execution in some heap layouts, an outright crash in others.

Know when Chrome gets its next vulnerability

  • 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

Vendor (google) PRIMARY 8.8 HIGH
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
vuln.today AI 8.8 HIGH

Reachable from a web page with no auth (AV:N/PR:N) but needs the victim to load it (UI:R); UAF yields full control of the renderer process, but impact stays within the sandbox (S:U).

3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (google).

CVSS VectorVendor: google

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

3
CVSS changed
Oct 21, 2026 - 00:23 NVD
8.8 (HIGH)
Patch available
Oct 20, 2026 - 23:20 EUVD
CVE Published
Oct 20, 2026 - 22:19 cve.org
HIGH 8.8

DescriptionCVE.org

Use after free in Extensions 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: Medium)

Executive ViewAI

Why It Matters

Google Chrome versions prior to 156.0.8078.47 contain a memory-corruption flaw in the Extensions component that could allow an attacker who lures a user to a crafted web page to execute code inside the browser's renderer sandbox and potentially crash the browser. The exposure is broad because Chrome is widely deployed, but sandbox confinement limits impact to the browser process, and no public exploit identified at time of analysis. Leadership should prioritize rapid patching to reduce user-level risk while recognizing that full host compromise would require an additional sandbox escape.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.4%
Top 68% exploitable
Prevalence
Ubiquitous
Google Chrome is the dominant desktop browser across virtually all environments
Data Quality
4 sources
Confidence: Medium

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.4%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

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.

More in Chrome

View all
CVE-2015-5122 CRITICAL POC
9.8 Jul 14

Use-after-free vulnerability in the DisplayObject class in the ActionScript 3 (AS3) implementation in Adobe Flash Player

CVE-2016-5198 HIGH POC
8.8 Jan 19

V8 in Google Chrome prior to 54.0.2840.90 for Linux, and 54.0.2840.85 for Android, and 54.0.2840.87 for Windows and Mac

CVE-2017-5070 HIGH POC
8.8 Oct 27

Type confusion in V8 in Google Chrome prior to 59.0.3071.86 for Linux, Windows, and Mac, and 59.0.3071.92 for Android, a

CVE-2016-1646 HIGH POC
8.8 Mar 29

The Array.prototype.concat implementation in builtins.cc in Google V8, as used in Google Chrome before 49.0.2623.108, do

CVE-2013-0758 CRITICAL POC
9.3 Jan 13

Mozilla Firefox before 18.0, Firefox ESR 10.x before 10.0.12 and 17.x before 17.0.2, Thunderbird before 17.0.2, Thunderb

CVE-2017-5030 HIGH POC
8.8 Apr 24

Incorrect handling of complex species in V8 in Google Chrome prior to 57.0.2987.98 for Linux, Windows, and Mac and 57.0.

CVE-2012-3993 CRITICAL POC
9.3 Oct 10

The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 16.0, Firefox ESR 10.x before 10.0.8, Thunderbi

CVE-2017-3823 HIGH POC
8.8 Feb 01

An issue was discovered in the Cisco WebEx Extension before 1.0.7 on Google Chrome, the ActiveTouch General Plugin Conta

CVE-2014-8636 HIGH POC
7.5 Jan 14

The XrayWrapper implementation in Mozilla Firefox before 35.0 and SeaMonkey before 2.32 does not properly interact with

CVE-2013-0757 CRITICAL POC
9.3 Jan 13

The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 18.0, Firefox ESR 17.x before 17.0.2, Thunderbi

CVE-2014-1510 CRITICAL POC
9.8 Mar 19

The Web IDL implementation in Mozilla Firefox before 28.0, Firefox ESR 24.x before 24.4, Thunderbird before 24.4, and Se

CVE-2015-5123 CRITICAL
9.8 Jul 14

Use-after-free vulnerability in the BitmapData class in the ActionScript 3 (AS3) implementation in Adobe Flash Player 13

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy