CVE-2025-2783

CRITICALNVD 8.39.0▲
EchelonGraph scoreHIGH confidence

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.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 5 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 9.2%CVSS: 8.3Exploit: cisa kev · ssvc active · epss top5pct · public exploitExposed services: Not assessed

A fix is available — apply it.

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)

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.0CRITICALhigh confidence
EG Risk
81
EG Risk 81/100CISA SSVC

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 computed
Severity90% × 45%
Exploitation100% × 40%
Automatability0% × 15%
CISA SSVC: Track at low, Attend at medium and Act at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
9.2%
EPSS %ILE
95th
KEV
⚠ Exploited

CISA SSVCTrack at low, Attend at medium and Act at high mission impact.

A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

March 26, 2025

Last Modified

October 24, 2025

Advisory Details (3)

Auto-updated Jun 2, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: cisa.
cisa Patch Available🔴 Active Exploitation

Known 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-2783
generic

Chromium

https://issues.chromium.org/issues/405143032
generic🔴 Active Exploitation

Chrome Releases: Stable Channel Update for Desktop

https://chromereleases.googleblog.com/2025/03/stable-channel-update-for-desktop_25.html

Vendor 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 108× in last 7d / 437× 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 1,688 total refreshes for this CVE.

  1. 2026-09-29 18:18 UTCEG score recompute
  2. 2026-09-29 18:18 UTCVendor advisory
  3. 2026-09-29 18:18 UTCGHSA enrichment
  4. 2026-09-29 15:19 UTCEPSS rescore
  5. 2026-09-29 14:29 UTCVendor advisory
  6. 2026-09-29 14:29 UTCGHSA enrichment
  7. 2026-09-29 10:41 UTCVendor advisory
  8. 2026-09-29 10:40 UTCGHSA enrichment
  9. 2026-09-29 06:48 UTCVendor advisory
  10. 2026-09-29 06:48 UTCGHSA enrichment
  11. 2026-09-29 03:00 UTCVendor advisory
  12. 2026-09-29 03:00 UTCGHSA enrichment
  13. 2026-09-28 23:12 UTCEG score recompute
  14. 2026-09-28 23:12 UTCVendor advisory
  15. 2026-09-28 23:11 UTCGHSA enrichment
  16. 2026-09-28 19:21 UTCVendor advisory
  17. 2026-09-28 19:21 UTCGHSA enrichment
  18. 2026-09-28 15:30 UTCEG score recompute
  19. 2026-09-28 15:30 UTCVendor advisory
  20. 2026-09-28 15:30 UTCGHSA enrichment
  21. 2026-09-28 13:50 UTCEPSS rescore
  22. 2026-09-28 11:42 UTCVendor advisory
  23. 2026-09-28 11:41 UTCGHSA enrichment
  24. 2026-09-28 07:52 UTCVendor advisory
  25. 2026-09-28 07:52 UTCGHSA enrichment
Show 75 more
  1. 2026-09-28 04:03 UTCVendor advisory
  2. 2026-09-28 04:03 UTCGHSA enrichment
  3. 2026-09-28 00:15 UTCVendor advisory
  4. 2026-09-28 00:15 UTCGHSA enrichment
  5. 2026-09-27 21:51 UTCCISA KEV update
  6. 2026-09-27 20:26 UTCVendor advisory
  7. 2026-09-27 20:26 UTCGHSA enrichment
  8. 2026-09-27 16:37 UTCEG score recompute
  9. 2026-09-27 16:37 UTCVendor advisory
  10. 2026-09-27 16:37 UTCGHSA enrichment
  11. 2026-09-27 12:49 UTCVendor advisory
  12. 2026-09-27 12:49 UTCGHSA enrichment
  13. 2026-09-27 09:01 UTCVendor advisory
  14. 2026-09-27 09:01 UTCGHSA enrichment
  15. 2026-09-27 05:11 UTCVendor advisory
  16. 2026-09-27 05:11 UTCGHSA enrichment
  17. 2026-09-27 01:21 UTCVendor advisory
  18. 2026-09-27 01:20 UTCGHSA enrichment
  19. 2026-09-26 21:30 UTCVendor advisory
  20. 2026-09-26 21:30 UTCGHSA enrichment
  21. 2026-09-26 17:42 UTCEG score recompute
  22. 2026-09-26 17:42 UTCVendor advisory
  23. 2026-09-26 17:41 UTCGHSA enrichment
  24. 2026-09-26 15:58 UTCEPSS rescore
  25. 2026-09-26 15:58 UTCEPSS rescore
  26. 2026-09-26 13:50 UTCVendor advisory
  27. 2026-09-26 13:50 UTCGHSA enrichment
  28. 2026-09-26 10:00 UTCVendor advisory
  29. 2026-09-26 10:00 UTCGHSA enrichment
  30. 2026-09-26 06:10 UTCVendor advisory
  31. 2026-09-26 06:09 UTCGHSA enrichment
  32. 2026-09-26 02:20 UTCEG score recompute
  33. 2026-09-26 02:20 UTCVendor advisory
  34. 2026-09-26 02:19 UTCGHSA enrichment
  35. 2026-09-26 00:24 UTCEPSS rescore
  36. 2026-09-26 00:24 UTCEPSS rescore
  37. 2026-09-25 22:31 UTCVendor advisory
  38. 2026-09-25 22:31 UTCGHSA enrichment
  39. 2026-09-25 19:35 UTCCISA KEV update
  40. 2026-09-25 18:43 UTCVendor advisory
  41. 2026-09-25 18:43 UTCGHSA enrichment
  42. 2026-09-25 14:55 UTCCISA KEV update
  43. 2026-09-25 14:54 UTCVendor advisory
  44. 2026-09-25 14:54 UTCGHSA enrichment
  45. 2026-09-25 11:05 UTCGHSA enrichment
  46. 2026-09-25 07:17 UTCVendor advisory
  47. 2026-09-25 07:17 UTCGHSA enrichment
  48. 2026-09-25 03:29 UTCVendor advisory
  49. 2026-09-25 03:29 UTCGHSA enrichment
  50. 2026-09-24 23:40 UTCVendor advisory
  51. 2026-09-24 23:40 UTCGHSA enrichment
  52. 2026-09-24 19:52 UTCVendor advisory
  53. 2026-09-24 19:52 UTCGHSA enrichment
  54. 2026-09-24 19:31 UTCCISA KEV update
  55. 2026-09-24 16:03 UTCEG score recompute
  56. 2026-09-24 16:03 UTCVendor advisory
  57. 2026-09-24 16:03 UTCGHSA enrichment
  58. 2026-09-24 14:02 UTCEPSS rescore
  59. 2026-09-24 12:15 UTCVendor advisory
  60. 2026-09-24 12:15 UTCGHSA enrichment
  61. 2026-09-24 08:26 UTCVendor advisory
  62. 2026-09-24 08:26 UTCGHSA enrichment
  63. 2026-09-24 04:38 UTCVendor advisory
  64. 2026-09-24 04:38 UTCGHSA enrichment
  65. 2026-09-24 00:49 UTCVendor advisory
  66. 2026-09-24 00:49 UTCGHSA enrichment
  67. 2026-09-23 21:01 UTCVendor advisory
  68. 2026-09-23 21:01 UTCGHSA enrichment
  69. 2026-09-23 17:13 UTCEG score recompute
  70. 2026-09-23 17:13 UTCVendor advisory
  71. 2026-09-23 17:12 UTCGHSA enrichment
  72. 2026-09-23 13:47 UTCEPSS rescore
  73. 2026-09-23 13:24 UTCVendor advisory
  74. 2026-09-23 13:24 UTCGHSA enrichment
  75. 2026-09-23 09:36 UTCVendor advisory

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-2783
    First seen Apr 1, 2026

    Full-chain exploit for CVE-2025-2783 (Ipcz Sandbox Escape & RCE).

    Open source ↗
  • Exploit-DBEDB-52403
    First seen Aug 11, 2025

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

    Open source ↗
  • GitHub PoCbyteReaper77/CVE-2025-2783
    First 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-2783
    First 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?
CVE-2025-2783 is a critical vulnerability published on March 26, 2025. 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)
When was CVE-2025-2783 disclosed?
CVE-2025-2783 was first published on March 26, 2025, with the most recent update on October 24, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-2783 actively exploited?
Yes. CISA added CVE-2025-2783 to the Known Exploited Vulnerabilities catalog on March 27, 2025, affecting Google Chromium Mojo. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2025-2783?
CVE-2025-2783 has a CVSS v3 base score of 8.3 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2025-2783?
CVE-2025-2783 affects Google Chromium Mojo.
How do I remediate CVE-2025-2783?
A fix for CVE-2025-2783 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-2783 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-2783

Explore →

Is Your Infrastructure Affected by CVE-2025-2783?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs