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)
CVE-2025-2783
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2025-03-27), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 8.3 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.3
- Vendor severity
- HIGHper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: High)
- EG Score
- 9.0(high)
- EG Risk
- 81(Attend)EG Risk 81/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity90% × 45%Exploitation100% × 40%Automatability0% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 8%
- EPSS %ILE
- 94%
- KEV
- ⚠ Exploited
Published
March 26, 2025
Last Modified
October 24, 2025
Advisory Details (3)
Auto-updated Jun 2, 2026Known Exploited Vulnerabilities Catalog | CISA
Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-2783Chrome Releases: Stable Channel Update for Desktop
https://chromereleases.googleblog.com/2025/03/stable-channel-update-for-desktop_25.htmlVendor Advisories for CVE-2025-2783(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Data Freshness Timeline
(refreshed 98× in last 7d / 398× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 941 total refreshes for this CVE.
- 2026-08-08 14:13 UTCVendor advisory
- 2026-08-08 14:13 UTCGHSA enrichment
- 2026-08-08 10:24 UTCVendor advisory
- 2026-08-08 10:24 UTCGHSA enrichment
- 2026-08-08 06:35 UTCGHSA enrichment
- 2026-08-08 02:47 UTCVendor advisory
- 2026-08-08 02:47 UTCGHSA enrichment
- 2026-08-07 22:58 UTCGHSA enrichment
- 2026-08-07 19:10 UTCEG score recompute
- 2026-08-07 19:10 UTCVendor advisory
- 2026-08-07 19:10 UTCGHSA enrichment
- 2026-08-07 17:09 UTCCISA KEV update
- 2026-08-07 16:26 UTCEPSS rescore
- 2026-08-07 15:21 UTCGHSA enrichment
- 2026-08-07 11:33 UTCVendor advisory
- 2026-08-07 11:33 UTCGHSA enrichment
- 2026-08-07 07:42 UTCVendor advisory
- 2026-08-07 07:42 UTCGHSA enrichment
- 2026-08-07 03:53 UTCVendor advisory
- 2026-08-07 03:53 UTCGHSA enrichment
- 2026-08-07 00:04 UTCVendor advisory
- 2026-08-07 00:04 UTCGHSA enrichment
- 2026-08-06 20:16 UTCVendor advisory
- 2026-08-06 20:16 UTCGHSA enrichment
- 2026-08-06 16:27 UTCEG score recompute
Show 75 moreShow fewer
- 2026-08-06 16:27 UTCVendor advisory
- 2026-08-06 16:27 UTCGHSA enrichment
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 12:38 UTCVendor advisory
- 2026-08-06 12:38 UTCGHSA enrichment
- 2026-08-06 08:50 UTCVendor advisory
- 2026-08-06 08:50 UTCGHSA enrichment
- 2026-08-06 05:01 UTCVendor advisory
- 2026-08-06 05:01 UTCGHSA enrichment
- 2026-08-06 01:13 UTCVendor advisory
- 2026-08-06 01:13 UTCGHSA enrichment
- 2026-08-05 21:24 UTCEG score recompute
- 2026-08-05 21:24 UTCVendor advisory
- 2026-08-05 21:24 UTCGHSA enrichment
- 2026-08-05 19:16 UTCEPSS rescore
- 2026-08-05 17:36 UTCGHSA enrichment
- 2026-08-05 17:25 UTCCISA KEV update
- 2026-08-05 13:47 UTCVendor advisory
- 2026-08-05 13:47 UTCGHSA enrichment
- 2026-08-05 09:58 UTCVendor advisory
- 2026-08-05 09:58 UTCGHSA enrichment
- 2026-08-05 06:08 UTCVendor advisory
- 2026-08-05 06:08 UTCGHSA enrichment
- 2026-08-05 02:19 UTCVendor advisory
- 2026-08-05 02:19 UTCGHSA enrichment
- 2026-08-04 22:30 UTCVendor advisory
- 2026-08-04 22:30 UTCGHSA enrichment
- 2026-08-04 18:42 UTCEG score recompute
- 2026-08-04 18:42 UTCVendor advisory
- 2026-08-04 18:42 UTCGHSA enrichment
- 2026-08-04 17:02 UTCCISA KEV update
- 2026-08-04 15:09 UTCEPSS rescore
- 2026-08-04 14:53 UTCVendor advisory
- 2026-08-04 14:53 UTCGHSA enrichment
- 2026-08-04 11:04 UTCEG score recompute
- 2026-08-04 11:04 UTCVendor advisory
- 2026-08-04 11:04 UTCGHSA enrichment
- 2026-08-04 10:37 UTCEPSS rescore
- 2026-08-04 07:16 UTCGHSA enrichment
- 2026-08-04 03:26 UTCGHSA enrichment
- 2026-08-03 23:37 UTCVendor advisory
- 2026-08-03 23:37 UTCGHSA enrichment
- 2026-08-03 19:49 UTCGHSA enrichment
- 2026-08-03 19:22 UTCCISA KEV update
- 2026-08-03 16:00 UTCGHSA enrichment
- 2026-08-03 12:11 UTCEG score recompute
- 2026-08-03 12:11 UTCVendor advisory
- 2026-08-03 12:11 UTCGHSA enrichment
- 2026-08-03 10:35 UTCEPSS rescore
- 2026-08-03 08:21 UTCVendor advisory
- 2026-08-03 08:21 UTCGHSA enrichment
- 2026-08-03 04:33 UTCVendor advisory
- 2026-08-03 04:33 UTCGHSA enrichment
- 2026-08-03 00:44 UTCVendor advisory
- 2026-08-03 00:44 UTCGHSA enrichment
- 2026-08-02 20:55 UTCVendor advisory
- 2026-08-02 20:55 UTCGHSA enrichment
- 2026-08-02 17:07 UTCVendor advisory
- 2026-08-02 17:07 UTCGHSA enrichment
- 2026-08-02 13:18 UTCVendor advisory
- 2026-08-02 13:18 UTCGHSA enrichment
- 2026-08-02 09:29 UTCVendor advisory
- 2026-08-02 09:29 UTCGHSA enrichment
- 2026-08-02 05:40 UTCEG score recompute
- 2026-08-02 05:40 UTCVendor advisory
- 2026-08-02 05:40 UTCGHSA enrichment
- 2026-08-02 02:26 UTCEPSS rescore
- 2026-08-02 01:52 UTCVendor advisory
- 2026-08-02 01:52 UTCGHSA enrichment
- 2026-08-01 22:03 UTCVendor advisory
- 2026-08-01 22:03 UTCGHSA enrichment
- 2026-08-01 18:14 UTCVendor advisory
- 2026-08-01 18:14 UTCGHSA enrichment
- 2026-08-01 14:25 UTCVendor advisory
- 2026-08-01 14:25 UTCGHSA enrichment
Publicly available exploits
(4 references)Working exploit code is in the public domain (3 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCaronfour/CVE-2025-2783First seen Apr 1, 2026
Full-chain exploit for CVE-2025-2783 (Ipcz Sandbox Escape & RCE).
Open source ↗ - Exploit-DBEDB-52403First seen Aug 11, 2025
Microsoft Edge Renderer Process (Mojo IPC) 134.0.6998.177 - Sandbox Escape
Open source ↗ - GitHub PoCbyteReaper77/CVE-2025-2783First seen Jun 15, 2025
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.
Open source ↗ - GitHub PoCAlchemist3dot14/CVE-2025-2783First seen Apr 6, 2025
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.
Open source ↗
Frequently asked(6)
What is CVE-2025-2783?
When was CVE-2025-2783 disclosed?
Is CVE-2025-2783 actively exploited?
What is the CVSS score of CVE-2025-2783?
Which products are affected by CVE-2025-2783?
How do I remediate CVE-2025-2783?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2025-2783
Is Your Infrastructure Affected by CVE-2025-2783?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.