VDB

CVE-2026-13854

CVE-2026-13854 PUBLISHED CVSS 9.6 CRITICAL

Reported by chrome · Published June 30, 2026

Use after free in Ozone in Google Chrome on Linux prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
chromiumChainguard150.0.7871.100-r2
chromiumWolfi150.0.7871.100-r2
ChromeGoogle150.0.7871.47

Risk scores

CVSS 3.1
9.6
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Affected products

VendorProductVersions
GoogleChrome150.0.7871.47
GoogleChrome150.0.7871.47
chainguardchromium0
wolfichromium0

Timeline

  • Jun 30, 2026 CVE Published
  • Jul 1, 2026 EPSS Score (22 in total, the first dated here)
  • Jul 1, 2026 Coalition ESS Score
  • Aug 11, 2026 Distribution Patch
  • Aug 11, 2026 Security Advisory (2 in total, the first dated here)
  • Oct 25, 2026 CVE Updated

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2026-13854
vulnetix vdb fixes CVE-2026-13854

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-13854/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›