CVE-2025-2783
KEVGoogle Chromium Mojo Sandbox Escape Vulnerability
Description
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.
Incorrect handle provided in unspecified circumstances in Mojo in Google Chrome on Windows prior to 134.0.6998.177 allowed a remote attacker to perform a sandbox escape via a malicious file. (Chromium security severity: High)
CVSS 3.1 vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:HPublishedMar 26, 2025
Last modifiedJun 17, 2026
Added to KEVMar 27, 2025
Remediation dueApr 17, 2025
References
- chromereleases.googleblog.com/2025/03/stable-channel-update-for-desktop_25.htmlRelease Notes
- issues.chromium.org/issues/405143032Permissions Required
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-2783US Government Resource
0 recent articles mention this CVE
72
Risk assessment · High
Actively exploited. Patch immediately.
- Exploitation
- Confirmed in the wild (CISA KEV)
- Federal remediation deadline
- Overdue by 558 days
- CVSS
- 8.3 HIGH
- EPSS (30-day exploit probability)
- 9.2% · top 5% of all CVEs
- Weakness
- NVD-CWE-noinfo
- Attack vector
- Network, remotely reachable
Recommended actions
- 1.Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
- 2.Treat as emergency change: patch or isolate internet-facing instances first.
- 3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
- 4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.
Assessment is derived automatically from the live signals above; verify against your own asset inventory.