VDB

CVE-2026-13976

CVE-2026-13976 PUBLISHED CVSS 5.8 MEDIUM

Reported by chrome · Published June 30, 2026

Insufficient data validation in Storage in Google Chrome 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: Medium)

Fixed versions

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

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

Risk scores

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

Affected products

VendorProductVersions
GoogleChrome150.0.7871.47
GoogleChrome150.0.7871.47
wolfichromium0
chainguardchromium0

Timeline

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

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2026-13976
vulnetix vdb fixes CVE-2026-13976

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-13976/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 ›