Google Chromium Mojo Sandbox Escape Vulnerability
Google — Chrome
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)
8.3
9.2%
Vector breakdown
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
- Published
- Mar 26, 2025
- Modified
- Jun 17, 2026
- Added to KEV
- Mar 27, 2025
- Federal patch due
- Apr 17, 2025
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.
Affected packages
Proof-of-concept & exploitation references
6 foundWeaponization
Public repositories whose name or description references CVE-2025-2783, found via a live GitHub search at request time. These are community-sourced signals, not a verified working exploit - cross-check each one before relying on it, and treat higher star counts and recent activity as (weak) corroboration, not proof.
- Alchemist3dot14/CVE-2025-2783★ 33
Simulated PoC for CVE-2025-2783 — a sandbox escape vulnerability in Chrome's Mojo IPC. Includes phishing delivery, memory fuzzing, IPC simulation, and logging. Safe for red team demos, detection engineering, and educational use.
updated Jul 27, 2026
- Leviticus-Triage/ChromSploit-Framework★ 17
Advanced AI-Powered Exploitation Framework | CVE-2025-4664 & CVE-2025-2783 & CVE-2025-2857 & CVE-2025-30397 |
updated Jul 27, 2026
- byteReaper77/CVE-2025-2783★ 8
This project is a research-oriented and educational simulation designed to demonstrate the concept of a sandbox escape vulnerability within Google Chrome (version 134.0.6998.177), leveraging improper handle , validation via Mojo IPC.
updated Mar 13, 2026
- bjrjk/CVE-2025-2783★ 1
Full-chain exploit for CVE-2025-2783 (Ipcz Sandbox Escape & RCE).
updated Aug 24, 2026
- ElianGonzi00/CVE-2025-2783★ 1
updated Oct 14, 2026
- razureink/cve-2025-2783-chrome_sandbox_escape_reproduction★ 0
CVE Reproduction: cve-2025-2783-chrome_sandbox_escape_reproduction
updated Jul 23, 2026
References
Frequently asked questions
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)
How severe is CVE-2025-2783?
CVE-2025-2783 has a CVSS base score of 8.3 out of 10 (CVSS 3.1).
Is CVE-2025-2783 actively exploited in the wild?
Yes. CVE-2025-2783 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added Mar 27, 2025, meaning CISA has confirmed evidence of active exploitation.
What is the EPSS score for CVE-2025-2783?
9.2% - meaning FIRST.org's EPSS model estimates a 9.2% probability this vulnerability will be exploited in the wild within 30 days (95% percentile among all scored CVEs).
Is there exploit tooling available for CVE-2025-2783?
We found 6 public GitHub repositories referencing CVE-2025-2783, though none matched a known Nuclei template or Metasploit module at last check. Review each one before relying on it - see the proof-of-concept section above.
Cross-checked against
Impactr finds and proves whether CVE-2025-2783 - or flaws like it - are actually reachable in your own web apps and APIs, with a reproducible exploit as evidence.
Join the waitlist