CVE-2026-110169: Use after free in V8 on 2026-09-28
Chromium CVE-2026-110169: Use after free
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 V8 in Google Chrome prior to 155.0.8059.79 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
— MITRE
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 155.0.4283.60 - Upgrade
Upgrade
Google Chrometo a version that resolves this vulnerability.Fixed in 155.0.8059.79
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2026-106200
- CVE-2026-106347
- CVE-2026-106204
- CVE-2026-106421
- CVE-2026-106383
- CVE-2026-106349
- CVE-2026-106184
- CVE-2026-106240
- CVE-2026-106358
- CVE-2026-106357
- CVE-2026-106190
- CVE-2026-106423
- CVE-2026-106346
- CVE-2026-106318
- CVE-2026-106411
- CVE-2026-106278
- CVE-2026-106233
- CVE-2026-106269
- CVE-2026-106268
- CVE-2026-106257
- CVE-2026-106235
- CVE-2026-106234
- CVE-2026-106248
- CVE-2026-106329
- CVE-2026-106211
- CVE-2026-106379
- CVE-2026-106227
- CVE-2026-106393
- CVE-2026-106255
- CVE-2026-106301
- CVE-2026-106226
- CVE-2026-106228
- CVE-2026-106244
- CVE-2026-106266
- CVE-2026-106181
- CVE-2026-106286
- CVE-2026-110171
- CVE-2026-110151
- CVE-2026-110167
- CVE-2026-110155
- CVE-2026-110154
- CVE-2026-110157
- CVE-2026-110148
- CVE-2026-110147
- CVE-2026-110138
- CVE-2026-110141
- CVE-2026-110163
- CVE-2026-110161
- CVE-2026-110136
- CVE-2026-110164
- CVE-2026-110172
- CVE-2026-110149
- CVE-2026-110168
- CVE-2026-110139
- CVE-2026-110166
- CVE-2026-110153
- CVE-2026-110159
- CVE-2026-110145
- CVE-2026-110158
- CVE-2026-110140
- CVE-2026-110137
- CVE-2026-110146
- CVE-2026-110143
- CVE-2026-110142
- CVE-2026-110160
- CVE-2026-110162
- CVE-2026-110170
- CVE-2026-110920
- CVE-2026-110921
- CVE-2026-110917
- CVE-2026-110918
- CVE-2026-110919
- CVE-2026-110922
- CVE-2026-110913
- CVE-2026-110914
- CVE-2026-110915
- CVE-2026-110916
- CVE-2026-113303
- CVE-2026-112993
- CVE-2026-113339
- CVE-2026-113179
- CVE-2026-113000
- CVE-2026-113212
- CVE-2026-113271
- CVE-2026-113280
- CVE-2026-113274
- CVE-2026-113072
- CVE-2026-113160
- CVE-2026-113279
- CVE-2026-113095
- CVE-2026-113019
- CVE-2026-113181
- CVE-2026-113154
- CVE-2026-113336
- CVE-2026-113161
- CVE-2026-113040
- CVE-2026-113175
- CVE-2026-113309
- CVE-2026-113192
- CVE-2026-113012
- CVE-2026-113086
- CVE-2026-113093
- CVE-2026-113338
- CVE-2026-113310
- CVE-2026-113318
- CVE-2026-113222
- CVE-2026-113020
- CVE-2026-113324
- CVE-2026-113253
- CVE-2026-113058
- CVE-2026-113098
- CVE-2026-113322
- CVE-2026-113104
- CVE-2026-113097
- CVE-2026-113206
- CVE-2026-113068
Frequently Asked Questions
What attacker interaction is required for exploitation?
A remote attacker needs a victim to process a crafted HTML page in Chrome. The reported impact is arbitrary code execution inside the browser sandbox.
Which Chrome installations should be prioritized for updating?
Google Chrome versions earlier than 155.0.8059.79 are affected. Update Chrome to 155.0.8059.79 or later.
Is this reported as a sandbox escape?
No. The stated code-execution impact is inside the sandbox; the provided information does not indicate escape from the Chrome sandbox.