SUSE · Security update for chromium
Affects SUSESource GCVE Database
Mentioned vulnerabilities
Not known to be exploited · CVSS 8.8 High.
Data as of 16 Nov 2026, 00:48 UTC
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
AI-suggested
Apply the security update to Chromium version 142.0.7444.59 or later stable releases where these vulnerabilities have been fixed. No additional mitigation steps are indicated beyond updating to the patched versions.
Description
This security update for Chromium addresses multiple vulnerabilities across various components including V8, WebGPU, Views, Omnibox, Media, Extensions, Storage, PageInfo, Ozone, App-Bound Encryption, Autofill, WebXR, Fullscreen UI, and SplitView. The issues fixed include type confusion, inappropriate implementations, out of bounds reads and writes, race conditions, use after free, policy bypasses, and incorrect security UI. These fixes are included in Chromium versions 142.0.7444.59 and later stable releases.
References
- suse.com/support/security/rating/ (opens in a new tab)
- ftp.suse.com/pub/projects/security/csaf/2026/opensuse-su-2025_20076-1.json (opens in a new tab)
- bugzilla.suse.com/1252881 (opens in a new tab)
- bugzilla.suse.com/1253089 (opens in a new tab)
- bugzilla.suse.com/1253267 (opens in a new tab)
- bugzilla.suse.com/1253698 (opens in a new tab)
- suse.com/security/cve/CVE-2025-12428/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-12429/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-12430/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-12431/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-12432/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-12433/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-12434/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-12435/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-12436/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-12437/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-12438/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-12439/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-12440/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-12441/ (opens in a new tab)