Summary
This update for chromium fixes the following issues:
Changes in chromium:
- Chromium 145.0.7632.159 (boo#1259213)
* CVE-2026-3536: Integer overflow in ANGLE
* CVE-2026-3537: Object lifecycle issue in PowerVR
* CVE-2026-3538: Integer overflow in Skia
* CVE-2026-3539: Object lifecycle issue in DevTools
* CVE-2026-3540: Inappropriate implementation in WebAudio
* CVE-2026-3541: Inappropriate implementation in CSS
* CVE-2026-3542: Inappropriate implementation in WebAssembly
* CVE-2026-3543: Inappropriate implementation in V8
* CVE-2026-3544: Heap buffer overflow in WebCodecs
* CVE-2026-3545: Insufficient data validation in Navigation
- Chromium 145.0.7632.116 (boo#1258733):
* CVE-2026-3061: Out of bounds read in Media
* CVE-2026-3062: Out of bounds read and write in Tint
* CVE-2026-3063: Inappropriate implementation in DevTools
- Chromium 145.0.7632.109 (boo#1258438):
* CVE-2026-2648: Heap buffer overflow in PDFium
* CVE-2026-2649: Integer overflow in V8
* CVE-2026-2650: Heap buffer overflow in Media
- more fixes for desktop file, some variables were lowercased,
further adaptions in INSTALL script (boo#1258199)
- also copy rollup into third_party/node/node_modules
- stay on llvm-10 for swiftshader but bring a similar patch
- drop use of rollup binaries and use rollup-3.x which does not
use prebuilt binaries (that fail at least on older ppc64le)
follow the approach of the debian packaging
- update/resync ppc64le patches from fedora
- fix INSTALL.sh again to replace the tags in desktop file,
appdata and manpage (boo#1258199)
- Chromium 145.0.7632.75:
* CVE-2026-2441: Use after free in CSS (boo#1258185)
- Chromium 145.0.7632.67:
* Revert a change in url_fixer that may have caused crashes
- Chromium 145.0.7632.45 (boo#1258116)
* jpeg-xl support has been readded
* CVE-2026-2313: Use after free in CSS
* CVE-2026-2314: Heap buffer overflow in Codecs
* CVE-2026-2315: Inappropriate implementation in WebGPU
* CVE-2026-2316: Insufficient policy enforcement in Frames
* CVE-2026-2317: Inappropriate implementation in Animation
* CVE-2026-2318: Inappropriate implementation in PictureInPicture
* CVE-2026-2319: Race in DevTools
* CVE-2026-2320: Inappropriate implementation in File input
* CVE-2026-2321: Use after free in Ozone
* CVE-2026-2322: Inappropriate implementation in File input
* CVE-2026-2323: Inappropriate implementation in Downloads
Fixed packages 1
| Release | Package | Fixed in |
|---|---|---|
| openSUSE · Leap 16.0 | chromium | 145.0.7632.159-bp160.1.1 |
Vulnerabilities 28
-
High 8.8
Use after free in CSS in Google Chrome prior to 145.0.7632.75 allowed a remote attacker to execute arbitrary code insid…
KEV Feb 17, 2026 -
Critical 9.6
Insufficient data validation in Navigation in Google Chrome prior to 145.0.7632.159 allowed a remote attacker to potent…
-
High 8.8
Use after free in CSS in Google Chrome prior to 145.0.7632.45 allowed a remote attacker to potentially exploit heap cor…
-
High 8.8
Heap buffer overflow in Codecs in Google Chrome prior to 145.0.7632.45 allowed a remote attacker to potentially exploit…
-
High 8.8
Inappropriate implementation in WebGPU in Google Chrome prior to 145.0.7632.45 allowed a remote attacker to potentially…
-
High 8.8
Use after free in Ozone in Google Chrome prior to 145.0.7632.45 allowed a remote attacker who convinced a user to engag…
-
High 8.8
Heap buffer overflow in PDFium in Google Chrome prior to 145.0.7632.109 allowed a remote attacker to perform an out of …
-
High 8.8
Integer overflow in V8 in Google Chrome prior to 145.0.7632.109 allowed a remote attacker to potentially exploit heap c…
-
High 8.8
Heap buffer overflow in Media in Google Chrome prior to 145.0.7632.109 allowed a remote attacker to potentially exploit…
-
High 8.8
Out of bounds read in Media in Google Chrome prior to 145.0.7632.116 allowed a remote attacker to perform an out of bou…
-
High 8.8
Out of bounds read and write in Tint in Google Chrome on Mac prior to 145.0.7632.116 allowed a remote attacker to perfo…
-
High 8.8
Inappropriate implementation in DevTools in Google Chrome prior to 145.0.7632.116 allowed an attacker who convinced a u…
-
High 8.8
Integer overflow in ANGLE in Google Chrome prior to 145.0.7632.159 allowed a remote attacker to potentially perform out…
-
High 8.8
Object lifecycle issue in PowerVR in Google Chrome on Android prior to 145.0.7632.159 allowed a remote attacker to pote…
-
High 8.8
Integer overflow in Skia in Google Chrome prior to 145.0.7632.159 allowed a remote attacker to potentially perform out …
-
High 8.8
-
High 8.8
Inappropriate implementation in WebAudio in Google Chrome prior to 145.0.7632.159 allowed a remote attacker to perform …
-
High 8.8
Inappropriate implementation in CSS in Google Chrome prior to 145.0.7632.159 allowed a remote attacker to perform an ou…
-
High 8.8
Inappropriate implementation in WebAssembly in Google Chrome prior to 145.0.7632.159 allowed a remote attacker to perfo…
-
High 8.8
Inappropriate implementation in V8 in Google Chrome prior to 145.0.7632.159 allowed a remote attacker to potentially pe…
-
High 8.8
Heap buffer overflow in WebCodecs in Google Chrome prior to 145.0.7632.159 allowed a remote attacker to perform an out …
-
High 7.5
Race in DevTools in Google Chrome prior to 145.0.7632.45 allowed a remote attacker who convinced a user to engage in sp…
-
Medium 6.5
Insufficient policy enforcement in Frames in Google Chrome prior to 145.0.7632.45 allowed a remote attacker to perform …
-
Medium 6.5
Inappropriate implementation in Animation in Google Chrome prior to 145.0.7632.45 allowed a remote attacker to leak cro…
-
Medium 6.5
Inappropriate implementation in PictureInPicture in Google Chrome prior to 145.0.7632.45 allowed a remote attacker who …
-
Medium 6.5
Inappropriate implementation in File input in Google Chrome prior to 145.0.7632.45 allowed a remote attacker who convin…
-
Medium 5.4
Inappropriate implementation in File input in Google Chrome prior to 145.0.7632.45 allowed a remote attacker who convin…
-
Medium 4.3
Inappropriate implementation in Downloads in Google Chrome prior to 145.0.7632.45 allowed a remote attacker to perform …
References
-
report
https://bugzilla.suse.com/1258116
-
report
https://bugzilla.suse.com/1258185
-
report
https://bugzilla.suse.com/1258199
-
report
https://bugzilla.suse.com/1258438
-
report
https://bugzilla.suse.com/1258733
-
report
https://bugzilla.suse.com/1259213
-
web
https://www.suse.com/security/cve/CVE-2026-2313
-
web
https://www.suse.com/security/cve/CVE-2026-2314
-
web
https://www.suse.com/security/cve/CVE-2026-2315
-
web
https://www.suse.com/security/cve/CVE-2026-2316
-
web
https://www.suse.com/security/cve/CVE-2026-2317
-
web
https://www.suse.com/security/cve/CVE-2026-2318
-
web
https://www.suse.com/security/cve/CVE-2026-2319
-
web
https://www.suse.com/security/cve/CVE-2026-2320
-
web
https://www.suse.com/security/cve/CVE-2026-2321
-
web
https://www.suse.com/security/cve/CVE-2026-2322
-
web
https://www.suse.com/security/cve/CVE-2026-2323
-
web
https://www.suse.com/security/cve/CVE-2026-2441
-
web
https://www.suse.com/security/cve/CVE-2026-2648
-
web
https://www.suse.com/security/cve/CVE-2026-2649
-
web
https://www.suse.com/security/cve/CVE-2026-2650
-
web
https://www.suse.com/security/cve/CVE-2026-3061
-
web
https://www.suse.com/security/cve/CVE-2026-3062
-
web
https://www.suse.com/security/cve/CVE-2026-3063
-
web
https://www.suse.com/security/cve/CVE-2026-3536
-
web
https://www.suse.com/security/cve/CVE-2026-3537
-
web
https://www.suse.com/security/cve/CVE-2026-3538
-
web
https://www.suse.com/security/cve/CVE-2026-3539
-
web
https://www.suse.com/security/cve/CVE-2026-3540
-
web
https://www.suse.com/security/cve/CVE-2026-3541
-
web
https://www.suse.com/security/cve/CVE-2026-3542
-
web
https://www.suse.com/security/cve/CVE-2026-3543
-
web
https://www.suse.com/security/cve/CVE-2026-3544
-
web
https://www.suse.com/security/cve/CVE-2026-3545