CVE-2026-106266: Confused deputy in Contextual Tasks on 2026-04-12
Chromium CVE-2026-106266: Confused deputy
Other sources
Confused deputy in Contextual Tasks in Google Chrome prior to 155.0.8059.39 allowed a remote attacker who had compromised the renderer process to bypass web origin policy into a privileged page via a crafted HTML page. (Chromium security severity: Medium)
— MITRE
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
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.45 - Upgrade
Upgrade
Google Chrometo a version that resolves this vulnerability.Fixed in 155.0.8059.39
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-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-110169
- 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
Who is realistically exposed to this issue?
The issue affects Google Chrome versions before 155.0.8059.39. Exploitation requires the attacker to have already compromised the renderer process, so it is primarily relevant as a follow-on privilege-boundary bypass rather than a standalone initial compromise.
What access does an attacker need to exploit it?
An attacker needs control of a compromised Chrome renderer process and a crafted HTML page. Under those conditions, they can bypass web origin policy into a privileged page.
What should be done to remediate the issue?
Update Google Chrome to version 155.0.8059.39 or later. The provided information does not describe a configuration workaround or mitigation for systems that cannot be updated immediately.