Skip to content
CTI Academy Sponsor CTI Academy
HIGH · CVSS 8.3 CISA Known Exploited Vulnerability

CVE-2025-2783

Google Chromium Mojo Sandbox Escape Vulnerability

Google Chromium Mojo

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
8.3
HIGH
EPSS
9.2%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
26 Mar 2025
NVD

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 27 March 2025. US federal agencies were required to remediate it by 17 April 2025.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 9.2%, which is higher than 95.4% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

Frequently asked questions

Is CVE-2025-2783 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2025-2783.

What does CVE-2025-2783 affect?

CVE-2025-2783 affects Google Chromium Mojo. 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)

How severe is CVE-2025-2783?

CVE-2025-2783 is rated HIGH with a CVSS base score of 8.3. EPSS puts the probability of exploitation in the next 30 days at 9.2%, higher than 95.4% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 17 April 2025.

How should organisations respond to CVE-2025-2783?

Apply the vendor patch for Google Chromium Mojo as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.