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?

Affected package information for CVE-2025-2783 is not yet fully mapped. Check the official advisory links for details.

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. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

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

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2025-2783?

O3 detects and blocks CVE-2025-2783 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

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 8.4%, placing it in the 94th 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·Added 2025-03-27 — agencies required to remediate by 2025-04-17

CVE-2025-2783

HIGH

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

0 pkgs

Patched

None yet

Exploits

3 known

EPSS Exploitation Probability

via FIRST.org ↗

8.4%probability of exploitation in next 30 days

Lower Risk94th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.
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
Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.
How O3 protects you
O3 detects and blocks CVE-2025-2783 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2025-2783. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Runtime Protection

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

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2025-2783 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.

Protect my workloads How runtime protection works