VDB

CVE-2026-11174

CVE-2026-11174 PUBLISHED CVSS 5.3 MEDIUM

Reported by chrome · Published June 4, 2026

Inappropriate implementation in Site Isolation in Google Chrome prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to bypass site isolation 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
chromiumWolfi149.0.7827.53-r0
chromiumChainguard149.0.7827.53-r0
chromegoogle149.0.7827.53

Risk scores

CVSS 3.1
5.3
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N

Affected products

VendorProductVersions
GoogleChrome149.0.7827.53
wolfichromium0
chainguardchromium0
GoogleChrome149.0.7827.53

Timeline

  • Jun 4, 2026 CVE Published
  • Jun 5, 2026 EPSS Score (15 in total, the first dated here)
  • Jun 7, 2026 Security Advisory (4 in total, the first dated here)
  • Jun 11, 2026 Coalition ESS Score
  • Aug 11, 2026 Distribution Patch
  • Sep 19, 2026 CVE Updated

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2026-11174
vulnetix vdb fixes CVE-2026-11174

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