CVE-2026-118332: Use after free in Compositing
Chromium: CVE-2026-118332 Improper input validation in Compositing
Other sources
Improper input validation in Compositing 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
Use after free in Compositing in Google Chrome prior to 156.0.8078.73 allowed a remote attacker who had compromised the renderer process to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)
— NVD
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
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
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
Google Chrometo a version that resolves this vulnerability.Fixed in 156.0.8078.73 - Upgrade
Upgrade
Microsoft Edge (Chromium-based)to 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-126901
- CVE-2026-126856
- CVE-2026-126887
- CVE-2026-121182
- CVE-2026-126859
- CVE-2026-121213
- CVE-2026-119267
- CVE-2026-126879
- CVE-2026-126869
- CVE-2026-110917
- CVE-2026-126863
- CVE-2026-121119
- CVE-2026-121061
- CVE-2026-118343
- CVE-2026-119270
- CVE-2026-121211
- CVE-2026-119260
- CVE-2026-113012
- CVE-2026-121076
- CVE-2026-118349
- CVE-2026-118318
- CVE-2026-118358
- CVE-2026-118346
- CVE-2026-113154
- CVE-2026-76031
- CVE-2026-76029
- CVE-2026-110170
- CVE-2026-118347
- CVE-2026-118357
- CVE-2026-113020
- CVE-2026-76024
- CVE-2026-118353
- CVE-2026-118334
- CVE-2026-113161
- CVE-2026-118331
- CVE-2026-118339
- CVE-2026-118307
- CVE-2026-119265
- CVE-2026-119266
- CVE-2026-113040
- CVE-2026-118304
- CVE-2026-118315
- CVE-2026-118342
- CVE-2026-110167
- CVE-2026-113095
- CVE-2026-113310
- CVE-2026-118341
- CVE-2026-118306
- CVE-2026-106269
- CVE-2026-118308
- CVE-2026-118337
- CVE-2026-118356
- CVE-2026-113309
- CVE-2026-118344
- CVE-2026-113336
- CVE-2026-118311
- CVE-2026-118317
- CVE-2026-113303
- CVE-2026-91718
- CVE-2026-87480
- CVE-2026-87651
Frequently Asked Questions
Which Chrome versions are affected?
Google Chrome versions before 156.0.8078.73 are affected. Updating to 156.0.8078.73 or later addresses the issue.
What would an attacker need to exploit this vulnerability?
An attacker would need to cause a victim to process a crafted HTML page remotely. Successful exploitation could potentially allow arbitrary code execution outside Chrome's sandbox.
How severe is this issue according to Chromium?
Chromium rates this vulnerability as High severity.