Live › vulnerability › CVE-2026-118321
Go to dashboardImproper input validation in the Core component of Google Chrome on Android, before 156.0.8078.73, lets a remote attacker run code outside the browser sandbox. The attack is triggered by a crafted HTML page the victim opens.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-27 23:29 UTC. All times on this page are UTC.
Anyone running Google Chrome on Android older than 156.0.8078.73 is exposed, since the flaw is in Chrome's core rendering and input handling. Exposure comes from browsing to a page an attacker controls, so any user who opens untrusted links is in scope. Devices already on 156.0.8078.73 or later can skip this; the sources do not address other Chromium-based browsers.
No product ranges from the sources yet.
adb shell dumpsys package com.android.chrome | grep versionName from a workstation156.0.8078.73; anything lower is affected156.0.8078.73 or later through the Play StoreEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
Improper input validation in Core in Google Chrome on on Android prior to 156.0.8078.73 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)
This page as .md · .json · in your agent: get_signal("CVE-2026-118321")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.