Skip to main content

Google Chrome CVE-2026-113307

| EUVDEUVD-2026-105560 HIGH
Buffer Overflow (CWE-119)
2026-10-20 chrome-cve-admin@google.com GHSA-6qx5-wv4c-c3cg
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 malicious web page
  2. Exploit
    Deliver crafted HTML to Extensions component
  3. Execution
    Trigger memory corruption (CWE-119)
  4. Impact
    Execute arbitrary code within renderer sandbox

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, buffer size validation
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 Google Chrome build (any version prior to 156.0.8078.47) that triggers memory corruption in the Extensions component - consistent with the CVSS UI:R flag, user interaction (navigating to or loading the malicious page) is mandatory, so this is not a zero-click flaw. No authentication or special configuration is required (PR:N), but the limiting factor is that the resulting code execution is explicitly confined to the renderer sandbox; absent a chained sandbox-escape, the attacker does not gain code execution on the underlying operating system.

Impact

Signals are mostly consistent toward a genuine high-priority browser flaw, with one important caveat. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R) describes a network-reachable, low-complexity, unauthenticated bug needing only that a victim load a crafted HTML page - the classic drive-by browser exploitation profile, scoring 8.8 (High). However, the description explicitly states the arbitrary code executes 'inside the sandbox,' and Chromium itself rated the issue only 'Medium' severity; a renderer-sandbox-confined RCE normally requires a second sandbox-escape bug to achieve full host compromise, so the C:H/I:H/A:H / S:U scoring reflects impact within the renderer rather than the underlying OS. This tension between the 8.8 base score and the sandbox-contained reality should be noted explicitly. No EPSS score, no CISA KEV listing, and no public POC were provided in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation. Given that the affected product is Google Chrome (near-ubiquitous) and a vendor patch is available, this warrants prompt patching, but in the absence of KEV/EPSS/POC data it should be treated as a routine-but-important browser update rather than an emergency, and the sandbox-only impact lowers the realistic standalone risk relative to the raw 8.8.

Exploit ScenarioDerived

An attacker hosts or compromises a web page containing malicious HTML that triggers the memory-corruption flaw in Chrome's Extensions component when a victim visits it with a vulnerable Chrome version (prior to 156.0.8078.47). Successful exploitation yields arbitrary code execution confined to the renderer sandbox, which an attacker would typically chain with a separate sandbox-escape to fully compromise the host. No public exploit code was identified in the provided data.

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

Memory corruption in Google Chrome's Extensions component (all builds prior to 156.0.8078.47) allows a remote attacker to execute arbitrary code inside the renderer sandbox by convincing a victim to load a crafted HTML page. Exploitation requires user interaction (CVSS UI:R) but no authentication or special configuration (PR:N), and the impact is bounded by Chrome's sandbox - absent a chained sandbox escape, the attacker does not obtain code execution on the underlying operating system. Google rates the Chromium security severity as Medium while the CVSS v3.1 base score is 8.8 (C:H/I:H/A:H); no public exploit code or confirmed active exploitation was identified at time of analysis, though the vendor has released a fixed build.

RemediationAI

Vendor-released patch: upgrade Google Chrome to 156.0.8078.47 or later - allow the browser's auto-update to apply it and fully restart all running Chrome processes (a relaunch is required for the fix to take effect), then confirm the installed build via chrome://version. Enterprise fleets should force the update through Google Update policies (UpdateDefault/ AutoUpdateCheckPeriodMinutes) or their software deployment tooling, and verify compliance rather than relying on user-initiated restarts. No vendor workaround is documented in the advisory, so compensating controls are limited: keep the browser out of privileged accounts, enforce site isolation and standard sandboxing (already default - do not disable with --no-sandbox), and for high-risk user groups restrict browsing to allow-listed destinations via proxy or DNS filtering to reduce exposure to crafted pages until the update lands, accepting the operational cost of reduced web reach. Detection-wise, correlate crashes or exploit telemetry in renderer processes for the Extensions component referenced in https://issues.chromium.org/issues/514066180, and treat any subsequent sandbox-escape chained to this bug as a host-compromise scenario.

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 class is CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer), i.e. classic memory corruption in native code reachable from the Extensions subsystem - the component that parses and brokers extension resources, bindings and renderer-side extension APIs inside Chromium. Because extension-related code is exposed to web content in the renderer, a crafted HTML page can drive the vulnerable path without any installed malicious extension. Google Chrome's multi-process architecture places this code in the renderer sandbox, so a successful exploit yields arbitrary code execution with renderer privileges only: reading/modifying same-origin data and the browser session, pivoting to further attacks, but not direct host compromise unless combined with a separate sandbox-escape vulnerability. The affected CPE class is Google Chrome desktop stable channel below version 156.0.8078.47; EUVD mirrors the same version boundary and links the vendor stable-channel advisory and the corresponding Chromium issue tracker entry (issues.chromium.org/issues/514066180).

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

Crafted HTML page is network-delivered and low-complexity with no auth (AV:N/AC:L/PR:N) but needs the victim to load it (UI:R); sandbox-confined RCE keeps scope unchanged with high renderer impact.

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

Memory corruption 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 earlier than 156.0.8078.47 carry a high-severity memory-safety defect in the Extensions component, creating a browser-session compromise risk for employees who visit crafted web content. The exposure is broad because Chrome is widely deployed, but the immediate blast radius is constrained by the browser sandbox and no public exploit was identified at time of analysis. Leadership should treat this as a patch-management priority for workforce endpoints, with residual concern focused on users who depend on Chrome for sensitive web access.

Business Impact: Medium
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.4%
Top 68% 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.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
Medium

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

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

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