CVE-2026-118307: High Use after free in Paint
Chromium: CVE-2026-118307 Use after free in Paint
Other sources
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 Paint in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
— NVD
Use after free in Paint 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
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 to a fixed release to a version that resolves this vulnerability.
Fixed in 156.0.8078.108 - 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-118331
- CVE-2026-118344
- CVE-2026-118348
- CVE-2026-113336
- CVE-2026-113338
- CVE-2026-113339
- CVE-2026-118304
- CVE-2026-118305
- CVE-2026-118308
- CVE-2026-118309
- CVE-2026-118310
- CVE-2026-118311
- CVE-2026-118313
- CVE-2026-118314
- CVE-2026-118315
- CVE-2026-118316
- CVE-2026-118317
- CVE-2026-118318
- CVE-2026-118319
- CVE-2026-118320
- CVE-2026-118321
- CVE-2026-118322
- CVE-2026-118327
- CVE-2026-118328
- CVE-2026-118329
- CVE-2026-118330
- CVE-2026-118332
- CVE-2026-118333
- CVE-2026-118334
- CVE-2026-118335
- CVE-2026-118336
- CVE-2026-118337
- CVE-2026-118339
- CVE-2026-118340
- CVE-2026-118341
- CVE-2026-118342
- CVE-2026-118343
- CVE-2026-118345
- CVE-2026-118346
- CVE-2026-118347
- CVE-2026-118349
- CVE-2026-118350
- CVE-2026-118351
- CVE-2026-118352
- CVE-2026-118353
- CVE-2026-118354
- CVE-2026-118355
- CVE-2026-118356
- CVE-2026-118357
- CVE-2026-118358
- CVE-2026-118359
- CVE-2026-121107
- CVE-2026-121113
- CVE-2026-121166
- CVE-2026-121174
- CVE-2026-121179
- CVE-2026-126882
- CVE-2026-130926
- CVE-2026-130952
- CVE-2026-130994
- CVE-2026-131004
- CVE-2026-131013
- CVE-2026-131023
- CVE-2026-131039
- CVE-2026-131044
- CVE-2026-131050
- CVE-2026-131063
- CVE-2026-131079
- CVE-2026-131092
- CVE-2026-131093
- CVE-2026-131100
- CVE-2026-131101
- CVE-2026-118312
- CVE-2026-118338
- CVE-2026-121102
- CVE-2026-121108
- CVE-2026-121161
- CVE-2026-121134
Frequently Asked Questions
Which Chrome versions need to be remediated?
Google Chrome versions prior to 156.0.8078.73 are affected. Update to 156.0.8078.73 or later.
What does an attacker need to exploit this issue?
An attacker would need to induce a user to load a crafted HTML page. Successful exploitation could potentially execute arbitrary code inside Chrome's sandbox.
Is this a sandbox escape?
No. The available information describes potential arbitrary code execution inside the sandbox; it does not state that an attacker can escape the sandbox or execute code at the operating-system level.