Google Chromium Mojo Sandbox Escape Vulnerability
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)
Severity = CVSS. Probability = EPSS (FIRST). Exploitation = public signals: KEV, EUVD, ransomware, EPSS above 10 %, no account required.
Exploitation probability EPSS · FIRST
Exploitation signals 3 / 5
- KEV catalog (CISA)27 Mar 2025
- Exploited in EUVD (ENISA)27 Mar 2025
- Used by ransomwareno
- EPSS above 10 %9.2%
- No account, over the networkyes
What to do
Fix
Apply the vendor’s fix as soon as it is available.
CISA guidance: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Meanwhile
Take the service off the internet or restrict access to it, watch the logs and look for signs of compromise.
Manufacturers (CRA)
Exploited vulnerability in your product: early warning to ENISA within 24 h, then notification within 72 h (Article 14 of the Cyber Resilience Act). The CRA explained
Affected products
- 134.0.6998.177 <134.0.6998.177
Open source packages OSV
Affected libraries according to OSV, with fixed versions.
Timeline
-
Published
-
Exploitation reported (ENISA)
-
Added to the KEV catalog
-
CISA remediation due date
References
Other exploited vulnerabilities from the same vendor
- CVE-2026-111497Google Brotli Unchecked Return Value Vulnerability8.6 · Rising fast
- CVE-2026-58704Google Pixel Improper Authorization Vulnerability4.7 · Actively exploited
- CVE-2026-87491Google Chromium V8 Out of Bounds Write Vulnerability5.4 · Actively exploited
- CVE-2026-85046Google Chromium V8 Type Confusion Vulnerability5.4 · Actively exploited
- CVE-2026-11645Google Chromium V8 Out-of-Bounds Read and Write Vulnerability5.4 · Actively exploited
- CVE-2026-5281Google Dawn Use-After-Free Vulnerability6.3 · Background exploitation