CVE-2025-4609

Exp

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: 2025-08-22 Last update: 2025-08-25 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-4609 is rated High Exploit Risk (63.5/100): CVSS Critical severity, with low exploitation likelihood (EPSS 0.36%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2025-4609

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2025-4609

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.03% 0.36% +0.33%
2 2026-03-21 0.11% 0.03% -0.08%
3 2025-08-26 — 0.11% —

Full EPSS history (5 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-4609

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.6 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 6.0 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-4609

OS Trackers for CVE-2025-4609

vendor priority summary link
alpine critical CVE-2025-4609: 1 source package rows (qt6-qtwebengine); 2 state rows across 2 repos (3.22-community, edge-community); fixed 2, open 0. https://security.alpinelinux.org/vuln/CVE-2025-4609
debian end-of-life CVE-2025-4609 end-of-life priority: Debian including 1 source packages (chromium), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2025-4609
ubuntu medium CVE-2025-4609 medium priority: Ubuntu including 1 source packages (chromium-browser), 6 status rows across 6 suites (focal, jammy, noble, oracular, plucky, upstream): not-affected 4, DNE 1, released 1. https://ubuntu.com/security/CVE-2025-4609

Affected software / configurations for CVE-2025-4609

Vendor Product Version Raw CPE
google chrome < 136.0.7103.113 cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*

References for CVE-2025-4609

cvelogic Threat Intelligence