# CVE-2025-2783: Google Chromium Mojo Sandbox Escape

> A remote attacker can escape the browser sandbox on Windows via a malicious file due to an incorrect handle in Mojo.

- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 27 Mar 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 26 Mar 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-hfqm-jfc6-rh2f, openSUSE-SU-2025:0111-1

## What is CVE-2025-2783?

CVE-2025-2783 is a high-severity vulnerability in Google Chrome, published on 26 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### 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)

## Which versions are affected by CVE-2025-2783?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `opera` | openSUSE:Leap 15.6 NonFree | All versions | 117.0.5408.163-lp156.2.32.1 |

Products: Google Chrome.

## How do I fix CVE-2025-2783?

Upgrade to a fixed version. US federal agencies must fix it by 17 Apr 2025.

## Is CVE-2025-2783 being exploited?

Yes. Attackers have exploited CVE-2025-2783 in the wild since at least 27 Mar 2025.

Public exploit code:

- 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. (github_poc): https://github.com/Alchemist3dot14/CVE-2025-2783
- 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. (github_poc): https://github.com/byteReaper77/CVE-2025-2783
-  Full-chain exploit for CVE-2025-2783 (Ipcz Sandbox Escape & RCE). (github_poc): https://github.com/bjrjk/CVE-2025-2783
- https://github.com/ElianGonzi00/CVE-2025-2783 (github_poc): https://github.com/ElianGonzi00/CVE-2025-2783
- Microsoft Edge Renderer Process (Mojo IPC) 134.0.6998.177 - Sandbox Escape (exploitdb)
- CVE Reproduction: cve-2025-2783-chrome_sandbox_escape_reproduction (github_poc): https://github.com/razureink/cve-2025-2783-chrome_sandbox_escape_reproduction

## Other vulnerabilities in Google Chrome

- [CVE-2022-4135](https://insights.sbomify.com/CVE-2022-4135/): Google Chromium GPU Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2020-16017](https://insights.sbomify.com/CVE-2020-16017/): Google Chrome Use-After-Free (critical 9.6, exploited in the wild)
- [CVE-2020-16010](https://insights.sbomify.com/CVE-2020-16010/): Google Chrome for Android UI Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2026-87491](https://insights.sbomify.com/CVE-2026-87491/): Google Chromium V8 Out of Bounds Write (high 8.8, exploited in the wild)
- [CVE-2026-85046](https://insights.sbomify.com/CVE-2026-85046/): Google Chromium V8 Type Confusion (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2783 and fix it if it is affected.

What it is: CVE-2025-2783 is a high-severity vulnerability in Google Chrome, published on 26 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2025-2783 in the wild since at least 27 Mar 2025.

Affected product: Google Chrome. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-2783/ (Markdown: https://insights.sbomify.com/CVE-2025-2783/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-2783
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-2783
- OSV: https://osv.dev/vulnerability/CVE-2025-2783

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-2783/
Summaries are generated and may contain mistakes; the official description above is the record.