SUSE · Security update for chromium
Affects SUSESource GCVE Database
Mentioned vulnerabilities
Not known to be exploited · CVSS 9.1 Critical.
Data as of 16 Nov 2026, 00:49 UTC
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 24 Sep 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 official Chromium updates starting from version 141.0.7390.122 and later, which include fixes for all listed vulnerabilities. Users and administrators should update their Chromium installations to these fixed versions to mitigate the risks. No additional mitigation steps are indicated beyond applying these security updates.
Description
Multiple security vulnerabilities affecting Chromium versions prior to 141.0.7390.122 have been addressed in a series of updates. These include heap buffer overflows, use-after-free bugs, side-channel information leaks, out-of-bounds reads, integer overflows, and inappropriate implementations in various components such as V8, Safe Browsing, Sync, Storage, WebCodecs, WebGPU, Video, Media, Omnibox, and Tab. The updates also resolve a privacy concern related to sending URLs as AI Mode input.
References
- suse.com/support/security/rating/ (opens in a new tab)
- ftp.suse.com/pub/projects/security/csaf/2026/opensuse-su-2025_20032-1.json (opens in a new tab)
- bugzilla.suse.com/1250472 (opens in a new tab)
- bugzilla.suse.com/1250780 (opens in a new tab)
- bugzilla.suse.com/1251334 (opens in a new tab)
- bugzilla.suse.com/1252013 (opens in a new tab)
- bugzilla.suse.com/1252402 (opens in a new tab)
- suse.com/security/cve/CVE-2025-10890/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-10891/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-10892/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-11205/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-11206/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-11207/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-11208/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-11209/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-11210/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-11211/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-11212/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-11213/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-11215/ (opens in a new tab)