Skip to content
Fencer Intel
high 8.3

CVE-2025-2783 kev in the critical feed json

Incorrect handle provided in unspecified circumstances in Mojo in Google Chrome on Windows prior to 134.0.6998.177 allowed a remote attacke…

published last yr. modified 4mo ago also EUVD-2025-8225

cvss
8.3
version 3.1, CNA
cisa kev
Exploited
added 2025-03-27
epss
9.2%
EPSS 9.2% chance of exploitation in 30 days, percentile 95%
public exploits
1
Exploit-DB

Summary

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)

Patch / fix

cisa required action Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

  • google chrome 134.0.6998.177
  • libqt5-qtwebengine openSUSE Tumbleweed 5.15.19-1.1
  • firefox-esr openSUSE Tumbleweed 128.9.0-1.1
  • opera openSUSE Leap 15.6 NonFree 117.0.5408.163-lp156.2.32.1

opensuse advisories openSUSE-SU-2025:15531-1openSUSE-SU-2025:14961-1openSUSE-SU-2025:0111-1

  • qt5-qtwebengine Alpine 3.21 5.15.17-r7
  • qt5-qtwebengine Alpine 3.23, Alpine 3.22 5.15.17-r10
  • qt6-qtwebengine Alpine 3.24, Alpine 3.23, Alpine 3.22 6.8.2-r3

alpine advisories ALPINE-CVE-2025-2783

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2025-2783 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-2783 updated

mojo: chromium: chromium Mojo on Windows

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. 0-day patched (Project Zero)
  2. Published
  3. Added to CISA KEV
  4. CISA SSVC: exploitation active
  5. CISA patch deadline
  6. First public exploit (EDB-52403)

Known exploited

Added
last yr.
Patch by
2025-04-17 (last yr.)
Ransomware
Not known
Required action
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Vendor, product
Google, Chromium Mojo
CISA name
Google Chromium Mojo Sandbox Escape Vulnerability

Zero-day

Detected in real attacks while still unknown to the vendor and the public, per Google Project Zero's 0day In-the-Wild tracker.

Patched
2025-03-25
Details
project zero tracker

ATT&CK techniques

How it is exploited and what it leads to, in MITRE ATT&CK terms.

  • T1203 Exploitation for Client Execution exploitation
  • T1548 Abuse Elevation Control Mechanism primary impact
  • T1497 Virtualization/Sandbox Evasion secondary impact

kev release 2025-07-28, att&ck v16.1. KEV to ATT&CK mappings by the MITRE Center for Threat-Informed Defense (Mappings Explorer, Apache-2.0). © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation. Terms of use

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

9.24% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-52403 Microsoft Edge Renderer Process (Mojo IPC) 134.0.6998.177 - Sandbox Escape webapps, 2025-08-11

CVSS scores

assigned by version score vector
CISA ADP 3.1 8.3 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
CNA 3.1 8.3 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

Affected products

  • Google Chrome

Classification

Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.