Skip to main content

Google Chrome CVE-2026-113341

| EUVDEUVD-2026-105618 MEDIUM
Buffer Overflow (CWE-119)
2026-10-20 chrome-cve-admin@google.com GHSA-j3wj-gcv7-gjjv
6.5
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
    Skia renders malicious graphics content
  3. Execution
    Trigger out-of-bounds read in Skia
  4. Impact
    Leak sandbox renderer memory to attacker

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 a victim using Google Chrome on Android (versions prior to 156.0.8078.47) to actively open or navigate to an attacker-controlled HTML page that triggers the Skia memory-corruption path - this user-interaction requirement (UI:R) is the primary limiting factor. No authentication and no special or non-default browser configuration is needed (PR:N), and the affected Skia rendering engine is active in default browsing. The impact is further LIMITED to reading memory within the renderer sandbox: it does not by itself grant sandbox escape, code execution, or data modification, so a successful attack yields information disclosure rather than full device compromise.

Impact

Signals are consistent and point to a moderate, not top-tier, priority. The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N, base 6.5) describes a network-reachable, low-complexity, unauthenticated flaw that requires user interaction and yields only a confidentiality impact - specifically an out-of-bounds memory READ confined inside the renderer sandbox, with no integrity or availability impact. This aligns with the description ('potentially read memory inside the sandbox'), so this is an information-disclosure primitive, not direct code execution. Note the divergence worth flagging: Chromium labels the issue 'Critical' severity while the CVSS base score is only 6.5 (Medium) - the vendor's rating reflects memory-safety class/upstream risk, whereas the CVSS reflects the constrained sandbox-read impact; treat the CVSS impact framing as the operational reality. EPSS is low at 0.24% (14th percentile), the CVE is NOT on CISA KEV, and no public exploit was identified, so there is no evidence of active or imminent widespread exploitation. The mitigating factor of required user interaction (UI:R) further lowers real-world urgency. Given Chrome's ubiquity, patch promptly through normal update cycles, but this does not warrant emergency out-of-band response on the available data.

Exploit ScenarioDerived

An attacker hosts a crafted HTML page that drives Chrome's Skia graphics library into a memory-corruption condition when rendered on an Android device. A victim who is lured to the page triggers an out-of-bounds read, letting the attacker leak memory contents from within the renderer sandbox (e.g., to defeat ASLR or harvest sensitive in-process data). No public exploit code was identified at time of analysis.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Oct 21, 2026

Improper bounds handling in the Skia graphics library lets a remote attacker who convinces a Chrome-for-Android user to open a crafted HTML page corrupt memory and read data from inside the renderer sandbox. The flaw affects Chrome on Android builds prior to 156.0.8078.47 and requires user interaction (UI:R) but no credentials or non-default configuration (PR:N), with the assessed impact limited to confidentiality loss (C:H) rather than code execution or sandbox escape. Google rates the underlying bug Critical internally and has shipped a fixed build; EPSS is low at 0.24% (14th percentile) and there is no KEV listing and no public exploit code identified at time of analysis.

RemediationAI

Vendor-released patch: upgrade Google Chrome on Android to 156.0.8078.47 or later via Google Play, and validate the installed version under Settings > About Chrome; managed fleets should force the update through Managed Google Play or an MDM policy so devices cannot remain on older builds. Where immediate patching is not possible, reduce exposure by restricting browsing to trusted sites and blocking untrusted content in high-risk environments - accepting that this sharply degrades usability and does not remove the Skia rendering path for allowed sites - and treat the bug as chainable by prioritizing it alongside sandbox-escape fixes, since Google's Critical rating reflects that potential. Monitor the Chromium issue at https://issues.chromium.org/issues/569165786 and the stable channel advisory at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html for any follow-up guidance; no vendor workaround short of upgrading was identified in the available data.

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

Skia is the open-source 2D graphics engine embedded in Chromium and Android, responsible for rasterizing everything from page content and canvas operations to fonts and images inside the renderer process. The root cause class, CWE-119 (improper restriction of operations within the bounds of a memory buffer), manifests here as a memory-corruption condition reachable through crafted HTML rendering the attacker controls, permitting reads of adjacent memory within the renderer's sandboxed address space. Because Chrome's renderer is sandboxed on Android, an out-of-bounds read is contained: the attacker obtains in-sandbox memory contents but gains no direct path to sandbox escape, code execution, or data modification, which is why the assessed vector scores C:H/I:N/A:N at 6.5 despite Google's internal 'Critical' Chromium severity (their scale anticipates chaining with a separate sandbox-escape bug). The CVSS vector AV:N/AC:L/PR:N/UI:R confirms a network-delivered, unauthenticated attack that hinges entirely on the victim navigating to the malicious page.

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 6.5 MEDIUM
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
vuln.today AI 6.5 MEDIUM

Remote crafted page with no auth gives AV:N/AC:L/PR:N, but requires the victim to open it (UI:R); impact is a sandbox-confined memory read, so C:H, I:N, A:N, S:U.

3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/VA:N/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
None
Availability
None

Lifecycle Timeline

4
CVSS changed
Oct 21, 2026 - 16:54 NVD
6.5 (MEDIUM)
Patch available
Oct 20, 2026 - 23:20 EUVD
CVE Published
Oct 20, 2026 - 22:19 cve.org
MEDIUM 6.5
CVE Published
Oct 20, 2026 - 22:19 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

Memory corruption in Skia in Google Chrome on on Android prior to 156.0.8078.47 allowed a remote attacker to potentially read memory inside the sandbox via a crafted HTML page. (Chromium security severity: Critical)

Threat Intelligence Overview

EPSS Score
0.2%
Top 86% exploitable
Prevalence
Ubiquitous
Google Chrome on Android 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 MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.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· derived
High

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
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.

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