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
What is CVE-2025-2783?
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.
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
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.