CVE-2026-110144: Incorrect authorization in Mojo
Chromium CVE-2026-110144: Incorrect authorization
Other sources
Incorrect authorization in Mojo in Google Chrome on on Windows prior to 155.0.8059.79 allowed a local attacker to potentially execute arbitrary code outside the sandbox via a local program. (Chromium security severity: High)
— 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
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 155.0.8059.79 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 155.0.4283.60 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 152.0.4191.137 - 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-110152
- CVE-2026-110149
- CVE-2026-110136
- CVE-2026-110161
- CVE-2026-110165
- CVE-2026-110148
- CVE-2026-110151
- CVE-2026-110162
- CVE-2026-110170
- CVE-2026-110160
- CVE-2026-110143
- CVE-2026-110146
- CVE-2026-110150
- CVE-2026-110156
- CVE-2026-110137
- CVE-2026-110140
- CVE-2026-110158
- CVE-2026-110145
- CVE-2026-110159
- CVE-2026-110153
- CVE-2026-110166
- CVE-2026-110169
- CVE-2026-110168
- CVE-2026-110139
- CVE-2026-110172
- CVE-2026-110164
- CVE-2026-110163
- CVE-2026-110141
- CVE-2026-110138
- CVE-2026-110157
- CVE-2026-110147
- CVE-2026-110154
- CVE-2026-110155
- CVE-2026-110167
- CVE-2026-110171
- CVE-2026-110142
Frequently Asked Questions
Which deployments are affected?
Google Chrome on Windows is affected when running a version earlier than 155.0.8059.79.
What does an attacker need to exploit this issue?
The attacker needs local access and a local program capable of exploiting the authorization flaw. The issue is not described as remotely exploitable.
What is the potential impact?
A successful exploit could potentially allow arbitrary code execution outside Chrome's sandbox.
How can I determine whether a system is affected?
Verify that the system is running Google Chrome on Windows and check its installed Chrome version. Versions earlier than 155.0.8059.79 are affected.
What should be done to remediate the issue?
Update Google Chrome on Windows to version 155.0.8059.79 or later.