Vulnerability · openSUSE-SU-2026:21514-1
Security update for chromium
Published Aug 1, 2026 · catalog updated Oct 31, 2026 · Security update for chromium
Last checked Nov 1, 2026. A connected source was read within the last 7 days.
Open the advisory
Exploitation likelihood is not on this record for openSUSE-SU-2026:21514-1. A missing EPSS score is not a low risk. Compare Security update for chromium with the linked advisory before you change production.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (Security update for chromium).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- EPSS is missing. A missing score is not a low risk.
- Severity
- Unknown—
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- Awaiting synchronization with FIRST
- Remediation
- Advisory link
- Affected products
- openSUSE:Leap 16.0 chromium
This update for chromium fixes the following issues: Changes in chromium: - Chromium 151.0.7922.71 (boo#1272936): * CVE-2026-17650: Use after free in Compositing * CVE-2026-17651: Insufficient validation of untrusted input in Dawn * CVE-2026-17652: Use after free in Views * CVE-2026-17653: Use after free in Skia * CVE-2026-17654: Race in Updater * CVE-2026-17655: Insufficient validation of untrusted input in ANGLE * CVE-2026-17656: Use after free in Ozone * CVE-2026-17657: Use after free in Navigation * CVE-2026-17658: Use after free in V8 * CVE-2026-17659: Inappropriate implementation in SiteIsolation * CVE-2026-17660: Insufficient validation of untrusted input in Network * CVE-2026-17661: Use after free in Loader * CVE-2026-17662: Insufficient policy enforcement in Prefetch * CVE-2026-17663: Insufficient validation of untrusted input in GPU * CVE-2026-17664: Insufficient validation of untrusted input in Loader * CVE-2026-17665: Use after free in V8 * CVE-2026-17666: Cryptographic Flaw in Enterprise * CVE-2026-17667: Uninitialized Use in ANGLE * CVE-2026-17668: Uninitialized Use in ANGLE * CVE-2026-17669: Inappropriate implementation in Chrome for iOS * CVE-2026-17670: Use after free in Views * CVE-2026-17671: Insufficient validation of untrusted input in ANGLE * CVE-2026-17672: Insufficient validation of untrusted input in Chromecast * CVE-2026-17673: Integer overflow in QUIC * CVE-2026-17674: Inappropriate implementation in HTML * CVE-2026-17675: Out of bounds write in ANGLE * CVE-2026-17676: Inappropriate implementation in ANGLE * CVE-2026-17677: Inappropriate implementation in ANGLE * CVE-2026-17678: Out of bounds read in ANGLE * CVE-2026-17679: Insufficient validation of untrusted input in Print Preview * CVE-2026-17680: Heap buffer overflow in Color * CVE-2026-17681: Insufficient validation of untrusted input in Web Authentication * CVE-2026-17682: Integer overflow in ANGLE * CVE-2026-17683: Inappropriate implementation in ANGLE * CVE-2026-17684: Insufficient
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- openSUSE:Leap 16.0 chromium0 → 151.0.7922.71-bp160.1.1
How to fix openSUSE-SU-2026:21514-1
Upgrade
openSUSE-SU-2026:21514-1 lists a fix boundary at 151.0.7922.71-bp160.1.1. Compare the installed build with that boundary before you change production.
Version check
Fixed in 151.0.7922.71-bp160.1.1
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
Exploitation likelihood is not on this record for openSUSE-SU-2026:21514-1. A missing EPSS score is not a low risk. Compare Security update for chromium with the linked advisory before you change production.
Which versions are affected?
Compare what you have installed with 0 → 151.0.7922.71-bp160.1.1. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Aug 1, 2026 · OpenSSF OSV / OSV Scanner
Detected
This update for chromium fixes the following issues: Changes in chromium: - Chromium 151.0.7922.71 (boo#1272936): * CVE-2026-17650: Use after free in Compositing * CVE-2026-17651: Insufficient validation of untrusted input in Dawn * CVE-2026-17652: Use after free in Views * CVE-2026-17653: Use after free in Skia * CVE-2026-17654: Race in Updater * CVE-2026-17655: Insufficient validation of untrust
Oct 31, 2026 · OpenSSF OSV / OSV Scanner
Fix available
chromium fixed in 151.0.7922.71-bp160.1.1
Oct 31, 2026 · OpenSSF OSV / OSV Scanner
Updated
This update for chromium fixes the following issues: Changes in chromium: - Chromium 151.0.7922.71 (boo#1272936): * CVE-2026-17650: Use after free in Compositing * CVE-2026-17651: Insufficient validation of untrusted input in Dawn * CVE-2026-17652: Use after free in Views * CVE-2026-17653: Use after free in Skia * CVE-2026-17654: Race in Updater * CVE-2026-17655: Insufficient validation of untrust
Oct 31, 2026 · OpenSSF OSV / OSV Scanner
Withdrawn
The advisory was withdrawn.
Sources
- OpenSSF OSV / OSV ScannerPackage advisoryopenSUSE-SU-2026:21514-1
Security update for chromium
osv.dev
References
Freshness
Last verified in this catalog Oct 31, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- OpenSSF OSV / OSV ScannerNov 1, 2026