Live › vulnerability › CVE-2025-2783
Go to dashboardGoogle Chromium's Mojo inter-process communication layer on Windows has a logic error where an incorrect handle is provided in unspecified circumstances, letting code break out of the browser sandbox. Attackers exploit it in the wild, and it can affect Chromium-based browsers such as Chrome, Edge and Opera.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:11 UTC, 3h before NVD. All times on this page are UTC.
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| Google Chromium Mojo | vendor | – | – |
| google chrome | vendor | < 134.0.6998.177 | 134.0.6998.177 |
Check the browser version under Help/About in Chrome, Edge or Opera on Windows and compare it with the fixed release in the vendor advisory.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Google Chromium Mojo on Windows contains a sandbox escape vulnerability caused by a logic error, which results from an incorrect handle being provided in unspecified circumstances. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.
CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
This page as .md · .json · in your agent: get_signal("CVE-2025-2783")
CISA KEV catalog, Creative Commons 0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.