CVE-2025-13631 json
Inappropriate implementation in Google Updater in Google Chrome on Mac prior to 143.0.7499.41 allowed a remote attacker to perform privileg…
published 11mo ago modified last mo. also EUVD-2025-200308
- cvss
- 8.8
- 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 36%
- public exploits
- 0
- none known
Summary
Inappropriate implementation in Google Updater in Google Chrome on Mac prior to 143.0.7499.41 allowed a remote attacker to perform privilege escalation via a crafted file. (Chromium security severity: High)
Patch / fix
- google chrome 143.0.7499.40, 143.0.7499.41
- chromium Debian 12 143.0.7499.40-1~deb12u1
- chromium Debian 13 143.0.7499.40-1~deb13u1
- chromium Debian 14 143.0.7499.40-1
debian advisories DEBIAN-CVE-2025-13631
- chromium openSUSE Leap 16.0 143.0.7499.192-bp160.1.1
- chromium openSUSE Tumbleweed 143.0.7499.40-2.1
opensuse advisories openSUSE-SU-2026:20020-1openSUSE-SU-2025:15794-1
Is CVE-2025-13631 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 FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 11mo ago
Exploit prediction
0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected products
- Google Chrome
Classification
- Technology feeds
References
-
chromereleases.googleblog.com
/2025/12/stable-channel-update-for-desktop.html
release-notes, vendor-advisory
-
issues.chromium.org
/issues/448113221
issue-tracking, permissions-required
Sources
- CVE List CVE-2025-13631
- NVD CVE-2025-13631
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.