CVE-2025-4052 in the critical feed json
Inappropriate implementation in DevTools in Google Chrome prior to 136.0.7103.59 allowed a remote attacker who convinced a user to engage i…
published last yr. modified 4mo ago also EUVD-2025-13448
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 46%
- public exploits
- 0
- none known
Summary
Inappropriate implementation in DevTools in Google Chrome prior to 136.0.7103.59 allowed a remote attacker who convinced a user to engage in specific UI gestures to bypass discretionary access control via a crafted HTML page. (Chromium security severity: Low)
Patch / fix
- google chrome 136.0.7103.59
- chromium Debian 12 136.0.7103.59-2~deb12u2
- chromium Debian 14, Debian 13 136.0.7103.59-2
debian advisories DEBIAN-CVE-2025-4052
- chromium Package Hub 15 SP6, openSUSE Leap 15.6 136.0.7103.59-bp156.2.113.2
- chromium openSUSE Tumbleweed 136.0.7103.59-1.1
opensuse advisories openSUSE-SU-2025:0145-1openSUSE-SU-2025:15051-1
- qt6-qtwebengine Alpine 3.24, Alpine 3.23, Alpine 3.22 6.8.2-r4
alpine advisories ALPINE-CVE-2025-4052
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-4052 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 FencerVendor 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-4052 updated cvss 8.8
chromium-browser: Inappropriate implementation in DevTools in Google Chrome
-
Red Hat All currently supported Red Hat productsnot 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
- yes
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.56% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Google Chrome
Classification
- Weakness
-
- CWE-838 Inappropriate Encoding for Output Context
- Technology feeds
References
-
chromereleases.googleblog.com
/2025/04/stable-channel-update-for-desktop_29.html
vendor-advisory
-
issues.chromium.org
/issues/401927528
permissions-required
Sources
- CVE List CVE-2025-4052
- NVD CVE-2025-4052
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.