Skip to main content

Chrome for Android CVE-2026-113055

| EUVDEUVD-2026-105475 HIGH
Access of Resource Using Incompatible Type (Type Confusion) (CWE-843)
2026-10-20 chrome-cve-admin@google.com GHSA-p6hw-p3m5-63hg
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 page
  2. Exploit
    Serve crafted HTML triggering FullScreen
  3. Execution
    Exploit type confusion (CWE-843)
  4. Impact
    Execute arbitrary code in renderer sandbox

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Type safety enforcement
MITRE ATT&CK

1 technique across 1 tactic: Execution

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 specifically crafted HTML page in a vulnerable Chrome for Android build (prior to 156.0.8078.47) that triggers the FullScreen type-confusion condition; no authentication is required (PR:N) but user interaction is mandatory (UI:R), since the attacker cannot force exploitation without the user visiting attacker-controlled content. The key limiting factors are: (1) resulting code execution is confined to the renderer sandbox (S:U) - no device-level compromise without a separate sandbox-escape chain; (2) it affects only the Android Chrome client at versions below the fixed release; and (3) it depends on luring the user to malicious or compromised web content rather than any server-side or default-on exposure.

Impact

Multiple signals point to a genuine but moderated priority. The NVD CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 8.8 HIGH) describes network-reachable, low-complexity exploitation with no privileges but requiring user interaction (visiting a crafted page). Importantly, Google rated the Chromium security severity as only MEDIUM, and the description states code execution occurs INSIDE the sandbox (S:U, scope unchanged) - meaning a sandbox escape is NOT part of this bug, which materially limits real-world impact versus the 8.8 score alone. This is the classic gap between a high NVD CVSS and the vendor's more conservative rating. No EPSS score, no CISA KEV listing, and no public POC were provided, so there is no evidence of active or imminent exploitation: no public exploit identified at time of analysis. No SSVC decision data was supplied. Net: a real memory-corruption RCE worth patching on normal Chrome cadence, but absent sandbox escape, KEV, or POC it is not an emergency - treat as routine browser patching rather than drop-everything. One data caveat: the only non-Chromium reference points to a DESKTOP stable-channel blog post while the CVE text specifies Android, so the exact advisory URL should be verified against the Android release notes.

Exploit ScenarioDerived

A victim using Chrome for Android (before 156.0.8078.47) is lured to a malicious or compromised website that serves a crafted HTML page exploiting the FullScreen type-confusion flaw (CWE-843), triggering arbitrary code execution within the renderer sandbox. Exploitation is remote and low-complexity but requires the user to visit the page (UI:R); code runs confined to the sandbox, so additional chained escapes would be needed for full device compromise. No public exploit code was identified at 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

Chrome for Android releases before 156.0.8078.47 contain a type-confusion flaw in FullScreen handling that can let a remote attacker execute arbitrary code inside the browser sandbox when a victim opens a crafted HTML page. Exploitation requires user interaction and no authentication, and any code execution is confined to the renderer sandbox absent a separate sandbox-escape chain. Vendor patches are available in 156.0.8078.47; no public exploit was identified at time of analysis.

RemediationAI

Update Chrome for Android to 156.0.8078.47 or later through Google Play; this is the vendor-released patch and resolves the FullScreen type-confusion issue. Managed environments should enforce browser version compliance and prioritize updates on devices exposed to untrusted web content. If immediate updating is not possible, reduce exposure by restricting browsing to trusted sites and preventing users from following untrusted links, recognizing that no documented feature toggle fully removes the attack surface; disabling FullScreen or restricting browser use would be disruptive and is not a substitute for patching. Vendor advisory: https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html.

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 issue is CWE-843 type confusion in Chromium's FullScreen component on Android. Type confusion occurs when code treats an object as a different type than it was allocated as, which can corrupt memory and provide a primitive for arbitrary code execution within the renderer. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) indicates network-delivered content, low attack complexity, no privileges, mandatory user interaction, and impact scoped to the vulnerable component; the sandbox boundary means host or device compromise would require an additional escape. Affected builds are Android Chrome versions below 156.0.8078.47; Chromium assigns Medium severity while the CVSS base score is 8.8.

Know when Android 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

Remote crafted-page delivery gives AV:N/AC:L/PR:N, visiting the page is UI:R, and sandbox-confined RCE keeps S:U with full C/I/A impact within the renderer.

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:18 cve.org
HIGH 8.8

DescriptionCVE.org

Type confusion in FullScreen in Google Chrome on on Android 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 for Android is affected by a high-severity code-execution flaw in FullScreen handling that could let a malicious webpage run code within the browser sandbox when a user opens a crafted page. Because mobile browsers are widely used for corporate email, SaaS, and web access, unpatched Android devices represent a material but manageable risk until updated to 156.0.8078.47 or later. No public exploit identified at time of analysis, and a vendor patch is available.

Business Impact: Medium
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.4%
Top 64% exploitable
Prevalence
Ubiquitous
Google Chrome is among the most widely deployed browsers globally
Data Quality
5 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

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.

CVE-2015-3105 CRITICAL POC
10.0 Jun 10

Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows and OS X and before 11.2.202.466

CVE-2015-3864 CRITICAL POC
10.0 Oct 01

Integer underflow in the MPEG4Extractor::parseChunk function in MPEG4Extractor.cpp in libstagefright in mediaserver in A

CVE-2013-4710 CRITICAL POC
9.3 Mar 03

Android 3.0 through 4.1.x on Disney Mobile, eAccess, KDDI, NTT DOCOMO, SoftBank, and other devices does not properly imp

CVE-2015-1538 CRITICAL POC
10.0 Oct 01

Integer overflow in the SampleTable::setSampleToChunkParams function in SampleTable.cpp in libstagefright in Android bef

CVE-2024-21633 HIGH POC
7.8 Jan 03

Apktool versions 2.9.1 and prior contain a path traversal vulnerability when processing Android APK files. Malicious APK

CVE-2017-13156 HIGH POC
7.8 Dec 06

An elevation of privilege vulnerability in the Android system (art). Rated high severity (CVSS 7.8), this vulnerability

CVE-2016-2107 MEDIUM POC
5.9 May 05

The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a

CVE-2015-3106 CRITICAL POC
10.0 Jun 10

Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows

CVE-2015-3107 CRITICAL POC
10.0 Jun 10

Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows

CVE-2013-4787 CRITICAL POC
9.3 Jul 09

Android 1.6 Donut through 4.2 Jelly Bean does not properly check cryptographic signatures for applications, which allows

CVE-2014-7911 HIGH
7.2 Dec 15

luni/src/main/java/java/io/ObjectInputStream.java in the java.io.ObjectInputStream implementation in Android before 5.0.

CVE-2016-0801 CRITICAL POC
9.8 Feb 07

The Broadcom Wi-Fi driver in the kernel in Android 4.x before 4.4.4, 5.x before 5.1.1 LMY49G, and 6.x before 2016-02-01

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