Vulnerability in Google Chrome
CVE-2025-4609
Incorrect handle provided in unspecified circumstances in Mojo in Google Chrome on Windows prior to 136.0.7103.113 allowed a remote attacker to potentially perform a sandbox escape via a malicious file. (Chromium security severity: High)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 9.6 (Critical). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H.
EPSS exploit prediction
EPSS 0.004, 34.3th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Google Chrome — versions 136.0.7103.113
Weakness classification (CWE)
Public exploits and proof-of-concept code
4 public repositories with exploit or proof-of-concept code for this CVE:
- vobando007/cve-2025-4609-mojo-poc (last pushed 2026-11-15): Mojo PoC for CVE-2025-4609
- vobando0077/cve-2025-4609-mojo-poc (last pushed 2026-11-12): Mojo PoC for CVE-2025-4609
- santiagovillalobos6900-commits/cve-2025-4609-mojo-poc (last pushed 2026-11-12)
- nek-3231/cve-2025-4609-mojo-poc (last pushed 2026-11-12)
Also mentioned in 6 other repositories (fkie-cad/nvd-json-data-feeds, gpxlnx/medium-writeup, hsamnguyen/lastest-update-bounty, …). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- chromereleases.googleblog.com/2025/05/stable-channel-update-for-desktop_14.html (Release Notes)
- issues.chromium.org/issues/412578726 (Exploit, Issue Tracking)
This CVE has public exploit evidence. See the latest CVEs with public exploits.