CVE-2026-118314: Incorrect reference resolution in UI
Chromium CVE-2026-118314: Incorrect reference resolution
Other sources
Improper input validation in UI in Google Chrome on on Android prior to 156.0.8078.73 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
— NVD
Incorrect reference resolution in UI in Google Chrome on on Android prior to 156.0.8078.73 allowed a local attacker leveraging social engineering to obtain sensitive information via a co-installed app. (Chromium security severity: High)
— NVD
This CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information.
— Microsoft
Credit
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 156.0.8078.73 - Upgrade
Upgrade
debian/chromiumto a version that resolves this vulnerability.Fixed in 156.0.8078.79-1~deb12u1Fixed in 156.0.8078.79-1~deb13u1Fixed in 156.0.8078.79-1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 156.0.4314.56 - Upgrade
Upgrade
debian/chromiumto a version that resolves this vulnerability.Fixed in 156.0.8078.73-1~deb12u1 - Upgrade
Upgrade
debian/chromiumto a version that resolves this vulnerability.Fixed in 156.0.8078.73-1~deb13u1 - Upgrade
Upgrade
debian/chromiumto a version that resolves this vulnerability.Fixed in 156.0.8078.73-1 - Upgrade
Upgrade
Google Chrome on Androidto a version that resolves this vulnerability.Fixed in 156.0.8078.73
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2026-118306
- CVE-2026-118331
- CVE-2026-118348
- CVE-2026-118344
- CVE-2026-118357
- CVE-2026-118318
- CVE-2026-118350
- CVE-2026-118339
- CVE-2026-118305
- CVE-2026-118317
- CVE-2026-118320
- CVE-2026-118322
- CVE-2026-118329
- CVE-2026-118354
- CVE-2026-118340
- CVE-2026-118321
- CVE-2026-118337
- CVE-2026-118352
- CVE-2026-118355
- CVE-2026-118307
- CVE-2026-118351
- CVE-2026-118328
- CVE-2026-118333
- CVE-2026-118336
- CVE-2026-118358
- CVE-2026-118353
- CVE-2026-118349
- CVE-2026-118327
- CVE-2026-118359
- CVE-2026-118343
- CVE-2026-118311
- CVE-2026-118334
- CVE-2026-118332
- CVE-2026-118313
- CVE-2026-118345
- CVE-2026-118304
- CVE-2026-118316
- CVE-2026-118346
- CVE-2026-118342
- CVE-2026-118310
- CVE-2026-118335
- CVE-2026-118308
- CVE-2026-118347
- CVE-2026-118341
- CVE-2026-118330
- CVE-2026-118315
- CVE-2026-118356
- CVE-2026-118309
- CVE-2026-118319
- CVE-2026-118312
- CVE-2026-118338
- DLA-4878-1
Frequently Asked Questions
Which deployments are affected?
Google Chrome on Android versions prior to 156.0.8078.73 are affected. The provided information does not identify other platforms as affected.
What does an attacker need to exploit this issue?
An attacker would need to induce a user to load a crafted HTML page remotely. The issue may allow arbitrary code execution inside the Chrome sandbox.
Is the browser sandbox fully bypassed by this vulnerability?
No full sandbox escape is stated. The described impact is arbitrary code execution inside the sandbox.