Skip to content
Fencer Intel
critical 9.6

CVE-2025-4609 in the critical feed json

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

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

cvss
9.6
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 33%
public exploits
0
none known

Summary

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)

Patch / fix

  • google chrome 136.0.7103.113
  • chromium Debian 12 136.0.7103.113-1~deb12u1
  • chromium Debian 14, Debian 13 136.0.7103.113-1

debian advisories DEBIAN-CVE-2025-4609

  • nodejs-electron openSUSE Tumbleweed 35.5.0-1.1
  • chromium openSUSE Tumbleweed 136.0.7103.113-1.1

opensuse advisories openSUSE-SU-2025:15182-1openSUSE-SU-2025:15143-1

  • qt6-qtwebengine Alpine 3.24, Alpine 3.23, Alpine 3.22 6.8.2-r4

alpine advisories ALPINE-CVE-2025-4609

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-4609 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-4609 updated cvss 8.8

chromium-browser: Incorrect handle provided in unspecified circumstances in Mojo

  • 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

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

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

Exploits and checks

  • issues.chromium.org https://issues.chromium.org/issues/412578726 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Affected products

  • Google Chrome

Classification

Weakness
  • CWE-732 Incorrect Permission Assignment for Critical Resource
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.