SUSE chromium · Security update for chromium
Affects SUSE chromiumSource GCVE Database
Mentioned vulnerabilities
Not known to be exploited · CVSS 5.4 Medium.
Data as of 5 Nov 2026, 23:24 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 6 Oct 2026
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 5 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
SUSEsuse/chromiumpkg:rpm/suse/chromiumOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A security update to Chromium version 155.0.8059.39 has been released that addresses all listed vulnerabilities. Users and administrators should apply this update promptly to mitigate the risks. No additional mitigation steps are indicated beyond applying the official update.
Description
A security update for Chromium version 155.0.8059.39 addresses multiple vulnerabilities including use-after-free, uninitialized resource, incorrect authorization, race conditions, information leaks, integer overflows, type confusion, improper input validation, missing authorization, confused deputy, code injection, and UI misrepresentation issues across various components such as Chromecast, Browser, ANGLE, Omnibox, V8, Media, PDF, and others. These vulnerabilities collectively pose critical security risks. The update promotes Chromium 155 to stable and fixes these issues.
References
- suse.com/support/security/rating/ (opens in a new tab)
- ftp.suse.com/pub/projects/security/csaf/opensuse-su-2026_22041-1.json (opens in a new tab)
- bugzilla.suse.com/1284354 (opens in a new tab)
- suse.com/security/cve/CVE-2026-106179/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-106180/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-106181/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-106182/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-106183/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-106184/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-106185/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-106186/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-106187/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-106188/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-106189/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-106190/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-106191/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-106192/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-106193/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-106194/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-106195/ (opens in a new tab)