How severe is CVE-2025-2783?

CVE-2025-2783 has a CVSS score of 8.3/10, rated HIGH. Immediate patching is strongly recommended.

Which products are affected by CVE-2025-2783?

CVE-2025-2783 affects the following products: google chrome.

How do I patch CVE-2025-2783?

Apply the google chrome security patch or hotfix for CVE-2025-2783 on the affected version, following the vendor advisory for your exact build.

How do I detect CVE-2025-2783 across my infrastructure?

Inventory every google chrome deployment and check each version against the affected-products list above.

How do I mitigate CVE-2025-2783 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Is CVE-2025-2783 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2025-2783, including 1 documented proof-of-concept exploit on Exploit-DB. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2025-2783?

CVE-2025-2783 has an EPSS (Exploit Prediction Scoring System) score of 9.2%, placing it in the 95th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is CVE-2025-2783 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2025-2783 (Google Chromium Mojo Sandbox Escape Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2025-03-27. CISA required all US federal civilian agencies to remediate this vulnerability by 2025-04-17. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

Which products and versions are affected by CVE-2025-2783?

CVE-2025-2783 affects google chrome. Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2025-2783 published, and has it been updated?

CVE-2025-2783 was published on March 26, 2025 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

CISA KEV · ACTIVELY EXPLOITED

HIGH severity

CVE-2025-2783 — CHROME

HIGH

CVE-2025-2783 is a high-severity (CVSS 8.3) vulnerability in google chrome. It is in CISA's Known Exploited Vulnerabilities catalog (added 2025-03-27) — treat it as actively exploited and patch now. A fix is available — see the affected versions and patch details below.

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…

Published

Mar 26, 2025

Updated

Jun 17, 2026

Affected

1 product

Patched

See advisory

Exploits

3 known

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2025-03-27. Federal agencies were required to remediate by 2025-04-17.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2025-2783.

EPSS Exploitation Probability

via FIRST.org ↗

9.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs95th percentile — riskier than 95% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2025-2783 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 394,803 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

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)

Affected Products

1 product · 1 configurations

Application

chromegoogle

< 134.0.6998.177

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-52403webappswindows

Microsoft Edge Renderer Process (Mojo IPC) 134.0.6998.177 - Sandbox Escape

by nu11secur1ty · Aug 11, 2025

Exploit-DB Source

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every google chrome deployment and check each version against the affected-products list above.
Fix
Apply the google chrome security patch or hotfix for CVE-2025-2783 on the affected version, following the vendor advisory for your exact build.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2025-2783 being exploited in your environment?

Detect and block the exploit chain at execution, on systems you cannot patch yet.

Protect my workloads How runtime protection works