CVE-2025-2783: Google Chromium Mojo Sandbox Escape
Google Chromium Mojo · listed in the CISA catalog of actively exploited vulnerabilities since 2025-03-27.
- CVSS v3.1 (CISA ADP)
- 8.3
- high
- EPSS (exploit probability, 30 days)
- 9.2%
- higher than 95.4% of all CVEs
- Added to CISA KEV
- 2025-03-27
- US federal due date 2025-04-17
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2025-2783 explained
CVE-2025-2783 is a sandbox escape vulnerability in Mojo in Google Chrome on Windows, caused by an incorrect handle provided in unspecified circumstances. A remote attacker can use a malicious file to break out of the browser sandbox. CISA lists it as known to be exploited, so affected browsers should be updated promptly.
Impact
A remote attacker who gets a user to open a malicious file can escape the Chrome sandbox. Attack complexity is high and user interaction is required, but no privileges are needed. Successful exploitation can affect systems beyond the browser and lead to high impact on confidentiality, integrity and availability. CISA rates the technical impact as total but not automatable. Attackers are known to use this vulnerability; ransomware use is unknown.
Who is affected
Google Chrome on Windows versions before 134.0.6998.177 are affected. The fix is included in Google Chrome 134.0.6998.177. The affected and fixed versions come from the CVE record published by its CNA (Chrome).
Written with AI from the data on this page and checked against it automatically.
Official 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)
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.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Google ChromeAffectedFixed in
- < 134.0.6998.177
- 134.0.6998.177
| Product | Affected | Fixed in |
|---|---|---|
| Google Chrome |
|
|
How to fix it
- Update to a fixed version: 134.0.6998.177.
- Vendor advisory: chromereleases.googleblog.com/2025/03/stable-channel-upda…
- CISA's deadline for US federal agencies: 2025-04-17 (passed) – a useful benchmark for everyone else, too.
What to do
- Update Google Chrome on Windows to
134.0.6998.177or later on all endpoints. - Restart the browser after updating so the fixed version is actually running.
- Verify fleet-wide browser versions through your management tools and remediate any systems still below
134.0.6998.177. - Follow the vendor advisory and CISA's required action; discontinue use if mitigations are unavailable.
- Warn users against opening untrusted files and check endpoints for signs of compromise.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Questions about CVE-2025-2783
- Is CVE-2025-2783 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-03-27, with a US federal due date of 2025-04-17. Whether it has been used in ransomware campaigns is unknown.
- Which version fixes the vulnerability?
- Google Chrome
134.0.6998.177contains the fix. Versions before134.0.6998.177on Windows are affected. - Does exploitation require user action?
- Yes. The attack requires user interaction, involving a malicious file, and has high attack complexity. No privileges are required.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.