Skip to main content

Google Chrome EUVDEUVD-2026-105638

| CVE-2026-113228 HIGH
Use After Free (CWE-416)
2026-10-20 chrome-cve-admin@google.com GHSA-v256-9p99-mwvp
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. Exploit
    Page triggers use-after-free in Network component
  3. Execution
    Reclaim freed object with controlled data
  4. Impact
    Execute arbitrary code inside 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 a user running an affected Chrome build (any version prior to 156.0.8078.47) to actively load attacker-controlled web content - the CVSS UI:R and the description's 'crafted HTML page' confirm victim interaction (visiting/rendering a page) is mandatory; it is not a zero-click flaw. No authentication or special privileges are needed (PR:N), and no non-default configuration is required since the affected Network component is core browser functionality. The principal limiting factor is that code execution is confined to the browser sandbox ('inside the sandbox'), so absent a separate sandbox-escape chain the attacker does not directly gain host-level access; updating to 156.0.8078.47 or later fully remediates.

Impact

Signals are mostly aligned toward a genuine but not top-tier priority. The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, score 8.8) indicates a network-reachable, low-complexity, unauthenticated flaw requiring only that a victim load a crafted HTML page - the classic browser drive-by profile. However, the Chromium team rated the security severity as Medium, and the description explicitly scopes code execution to 'inside the sandbox,' meaning the initial primitive is contained by Chrome's renderer sandbox (consistent with S:U/scope-unchanged). This tempers real-world impact: a sandbox escape or chained second bug would be needed for full host compromise, which is not described here. No EPSS score was supplied, so exploitation probability cannot be quantified. The CVE is NOT on CISA KEV and no public POC or exploit code is referenced, so this is 'no public exploit identified at time of analysis.' A patch is confirmed available from the vendor. Net: a real priority for patch management given ubiquitous deployment and a network/UI-only trigger, but the Medium Chromium rating plus sandbox containment and absence of exploitation evidence argue against emergency-level urgency. Note the apparent tension between the 8.8 CVSS and the vendor's Medium rating - the CVSS captures the in-sandbox C/I/A loss, not real-world blast radius, so treat 8.8 as an upper bound.

Exploit ScenarioDerived

An attacker hosts or compromises a web page containing specially crafted content that triggers a use-after-free in Chrome's Network component when the victim's browser processes it. The victim merely needs to visit the malicious page (user interaction required, no authentication), after which the attacker can execute arbitrary code within the browser sandbox. No public exploit code has been identified at the time of analysis.

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

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

Alert me

AnalysisAIv1 – Oct 21, 2026

Heap use-after-free in Google Chrome's Network component allows remote code execution within the browser sandbox: any Chrome build prior to 156.0.8078.47 that renders an attacker-crafted HTML page can trigger memory corruption and achieve code execution at the browser's privilege level. No credentials or privileges are required (PR:N), but exploitation is not zero-click - the victim must navigate to or load the malicious content, as reflected by CVSS UI:R and the vendor's 'crafted HTML page' wording. Chromium rates the issue Medium severity even though the CVSS 3.1 base score computes to 8.8 (C:H/I:H/A:H); no public exploit code or CISA KEV entry was identified at time of analysis, and the practical ceiling on impact is the Chrome sandbox, which must be escaped separately for host-level compromise.

RemediationAI

Vendor-released patch: Google Chrome 156.0.8078.47 (Stable channel, October 2026 update) - upgrade immediately via chrome://settings/help or your enterprise software-deployment channel, and confirm version 156.0.8078.47 or later on all managed endpoints; the release notes are at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html. Enforce browser auto-update through Google Update/Chrome Enterprise policies (e.g. RelaunchNotification and UpdateDefault) so the fix is applied without user action, since the attack only requires a victim to render a page. Organizations running Chromium-derived browsers (Edge, Brave, Opera, and embedded Chromium) must wait for their vendor to rebase onto 156.0.8078.47 and should track that rebase explicitly rather than assuming Chrome patching covers them. Interim compensating controls, all with trade-offs: keep Chrome's site isolation and sandbox enabled (disabling them for compatibility removes the primary containment boundary against this class of bug), restrict browsing to an allowlist of trusted sites or route untrusted traffic through a remote-rendering/isolation service (usability and performance cost), and reduce exposure by running high-risk browsing in a disposable VM or separate low-privilege profile (operational overhead). No workaround removes the defect itself; patching is the only complete fix, and because no public exploit code or KEV-listed active exploitation was identified at time of analysis, the patch cadence should follow normal enterprise SLAs rather than emergency out-of-band response.

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 flaw is CWE-416 (use-after-free), a memory-safety class in which an object freed during Network-stack processing - the component that handles HTTP(S) transactions, resource loading and response parsing - is referenced again after deallocation. An attacker who controls the HTML/response content can shape heap activity to reclaim the freed allocation with attacker-influenced data, then redirect a virtual call or write through the dangling pointer, yielding arbitrary code execution in the renderer/network context. Because the corruption occurs inside Chrome's multi-process sandbox, code execution is bounded by the sandbox's OS-level restrictions; host compromise requires an additional sandbox-escape primitive. The affected surface is core, default-enabled browser functionality present in every Chrome build before 156.0.8078.47 (CPE coverage per EUVD: Chrome < 156.0.8078.47), so no special configuration is needed to be exposed - only the willingness of a user to open hostile web content.

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

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

Remote crafted page (AV:N, AC:L, PR:N) requires the victim to open it (UI:R); code runs within the sandbox so scope is unchanged (S:U) with high in-renderer C/I/A.

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 Network 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 builds prior to 156.0.8078.47 are exposed to a high-severity memory-corruption flaw in the Network component that can let a crafted HTML page execute code at the browser's privilege level. This affects any user who browses to attacker-controlled content, so the organizational exposure tracks broadly deployed Chrome rather than a narrow server or administrative population. Leadership should prioritize rapid browser fleet remediation because of the large user base and potential for browser-level compromise, while recognizing that host compromise would require an additional sandbox escape and no public exploit was identified at time of analysis.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.3%
Top 76% exploitable
Prevalence
Ubiquitous
Google Chrome is among the most widely deployed browsers worldwide
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.3%
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.

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