CVE-2026-118336: Race condition in Headless
Chromium: CVE-2026-118336 Improper input validation in Headless
Other sources
Improper input validation in Headless in Google Chrome 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
Race condition in Headless in Google Chrome 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)
— 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.4314.56 - 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
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 Chrometo a version that resolves this vulnerability.Fixed in 156.0.8078.73
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- DLA-4878-1
- 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-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-118314
- 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
Frequently Asked Questions
Which Chrome deployments are affected?
The issue affects the Headless component in Google Chrome versions earlier than 156.0.8078.73. Deployments that do not use Headless are not identified as affected by the provided information.
What does an attacker need to exploit this issue?
An attacker would need to cause the target to process a crafted HTML page in Chrome Headless. The described impact is potential arbitrary code execution inside the sandbox.
What is the immediate remediation?
Update Google Chrome to version 156.0.8078.73 or later. The provided information does not specify an alternative mitigation if updating is not immediately possible.