Secuno
ENNL
Book demo

CVE-2025-2783

Google Chromium Mojo Sandbox Escape

8.3 HIGHActively exploited (CISA KEV)EPSS 9.24%
  1. Published26 Mar 2025
  2. Added to CISA KEV27 Mar 2025
  3. Remediation due17 Apr 2025
Actively exploited (CISA KEV)

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.

Added to KEV: 27 Mar 2025Federal remediation due: 17 Apr 2025

Description

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 breakdown

Attack vectorNetwork
Attack complexityHigh
Privileges requiredNone
User interactionRequired
ScopeChanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

Affected products

Google Chrome< 134.0.6998.177

Remediation

Fixed in
Google Chrome≥ 134.0.6998.177

References

Frequently asked

Is CVE-2025-2783 being actively exploited?

Yes. CVE-2025-2783 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added 27 Mar 2025.

How severe is CVE-2025-2783?

CVE-2025-2783 has a CVSS 3.1 base score of 8.3, rated high. EPSS estimates a 9.24% probability of exploitation.

Which products are affected by CVE-2025-2783?

Affected products include Google Chrome.

How do I fix CVE-2025-2783?

Upgrade affected software to a fixed version, for example Google Chrome 134.0.6998.177 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-2783 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. Because it is on the CISA KEV list, a risk for it never ranks below high, and the update that fixes it moves to the Emergency patch lane. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.