Vulnerability · 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
Published Aug 22, 2025 · catalog updated Feb 26, 2026 · Google Chrome
Last checked Oct 29, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2025-4609. EPSS is 0.39%. Act only if a listed version of Google Chrome is installed.
Gaps on this record
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2026-76024 · Medium
- CVE-2026-76025 · High
- CVE-2026-76026 · High
- CVE-2026-76027 · Medium
- CVE-2026-76028 · High
- Severity
- Critical9.6
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.39%
- Remediation
- Version ranges on file
- Affected products
- vendor Google Chrome 136.0.7103.113 <136.0.7103.113
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)
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- vendor Google Chrome 136.0.7103.113 <136.0.7103.113136.0.7103.113 <136.0.7103.113
How to fix CVE-2025-4609
Upgrade
CVE-2025-4609 lists a fix boundary at 136.0.7103.113. Compare the installed build with that boundary before you change production.
Version check
Seen in 136.0.7103.113 <136.0.7103.113
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2025-4609. EPSS is 0.39%. Act only if a listed version of Google Chrome is installed.
Which versions are affected?
Compare what you have installed with Google Chrome 136.0.7103.113 <136.0.7103.113 136.0.7103.113 <136.0.7103.113. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.39%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Aug 22, 2025 · EUVD
Detected
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)
Feb 26, 2026 · EUVD
Updated
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)
Sources
- CVE.orgVulnerability recordCVE-2025-4609
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2025-4609
30-day exploitation probability 0.39%
first.org - EUVDVulnerability recordEUVD-2025-25768
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)
euvd.enisa.europa.eu
References
Freshness
Last verified in this catalog Oct 29, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- FIRST EPSSOct 23, 2026
- CVE.orgOct 22, 2026
- EUVDOct 22, 2026