CVE-2026-14021

Published Jun 30, 2026 CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
Description
Insufficient policy enforcement in StorageAccessAPI in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: Medium)

Analysis

AI-generated

Technical impact

The vulnerability is an input‑validation weakness in Chrome’s StorageAccessAPI that allows a compromised renderer process to expose cross‑origin data when a specially crafted HTML page is loaded. Because the API does not enforce proper policy checks in versions prior to 150.0.7871.47, an attacker who has already managed to subvert a renderer can read data belonging to other origins. The result is unauthorized retrieval of potentially sensitive information, a clear compromise of confidentiality for the affected user. The weakness is classified as CWE‑20.

Affected Systems

Google Chrome installations with a version older than 150.0.7871.47 are affected. All older releases lack the policy enforcement that mitigates cross‑origin data leakage. Newer releases have the patch applied and are not vulnerable. The flaw is tied exclusively to the Chrome renderer component within those older versions.

Risk and Exploitability

The CVSS score of 6.5 indicates a moderate severity, while the EPSS of less than 1 % suggests a very low probability of exploitation in the wild. The flaw is not listed in the CISA KEV catalog. Exploitation requires an initial compromise of the renderer process, which typically limits the attack surface but still poses a risk to users who run unmanaged or malicious code that can target Chrome’s rendering engine. The primary attack vector is a crafted HTML page executed by the compromised renderer, allowing the attacker to trigger the StorageAccessAPI and read cross‑origin data.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update to Chrome version 150.0.7871.47 or later to apply the policy enforcement patch.
  • Terminate or isolate any Chrome renderer processes that may have been compromised to stop further data exposure.
  • Configure enterprise policies to disable or restrict StorageAccessAPI usage until the update is applied, reducing the attack surface for malicious pages.

Generated by OpenCVE AI on July 31, 2026 at 16:06 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4672-1 chromium security update
Debian DSA Debian DSA DSA-6378-1 chromium security update
History
Type Values Removed Values Added
Title Chrome StorageAccessAPI Cross‑Origin Data Leakage via Compromised Renderer
Type Values Removed Values Added
Title Chrome StorageAccessAPI Cross‑Origin Data Leakage via Compromised Renderer
Type Values Removed Values Added
Title Chrome StorageAccessAPI Weakness Enables Cross‑Origin Data Leakage
Type Values Removed Values Added
Title Chrome StorageAccessAPI Weakness Enables Cross‑Origin Data Leakage
Type Values Removed Values Added
Title Chrome StorageAccessAPI Policy Enforcement Flaw Exposes Cross‑Origin Data
Type Values Removed Values Added
Title Chrome StorageAccessAPI Policy Enforcement Flaw Exposes Cross‑Origin Data
Type Values Removed Values Added
Title Insufficient StorageAccessAPI Policy Enforcement Enables Cross‑Origin Data Leakage via Renderer Compromise
Type Values Removed Values Added
Title Insufficient StorageAccessAPI Policy Enforcement Enables Cross‑Origin Data Leakage via Renderer Compromise
Type Values Removed Values Added
Title Chrome StorageAccessAPI Cross‑Origin Data Leakage via Compromised Renderer
Type Values Removed Values Added
Title Chrome StorageAccessAPI Cross‑Origin Data Leakage via Compromised Renderer
Type Values Removed Values Added
Title Cross‑Origin Data Leak via StorageAccessAPI in Chrome
Type Values Removed Values Added
Title Cross‑Origin Data Leak via StorageAccessAPI in Chrome
Type Values Removed Values Added
Title Cross‑Origin Data Exfiltration via StorageAccessAPI in Chrome
Type Values Removed Values Added
Title Cross‑Origin Data Exfiltration via StorageAccessAPI in Chrome
Type Values Removed Values Added
Title Insufficient policy enforcement in Google Chrome’s StorageAccessAPI allows cross‑origin data leakage via crafted page
Type Values Removed Values Added
Title Insufficient policy enforcement in Google Chrome’s StorageAccessAPI allows cross‑origin data leakage via crafted page
Type Values Removed Values Added
Title Chrome Cross‑Origin Data Leak via StorageAccessAPI
Type Values Removed Values Added
Title Chrome Cross‑Origin Data Leak via StorageAccessAPI
Type Values Removed Values Added
Title Cross‑Origin Data Leakage via StorageAccessAPI in Google Chrome
Type Values Removed Values Added
Title Cross‑Origin Data Leakage via StorageAccessAPI in Google Chrome
Type Values Removed Values Added
Title Insufficient StorageAccessAPI Enforcement Enables Cross‑Origin Data Leakage in Chrome
Type Values Removed Values Added
Title Insufficient StorageAccessAPI Enforcement Enables Cross‑Origin Data Leakage in Chrome
Type Values Removed Values Added
Title Cross‑Origin Data Leakage via StorageAccessAPI in Chrome
Type Values Removed Values Added
Title Cross‑Origin Data Leakage via StorageAccessAPI in Chrome
Type Values Removed Values Added
Title Insufficient policy enforcement in Chrome StorageAccessAPI allows cross‑origin data leakage
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Title Insufficient policy enforcement in Chrome StorageAccessAPI allows cross‑origin data leakage
Type Values Removed Values Added
First Time appeared Google
Google chrome
Vendors & Products Google
Google chrome
Type Values Removed Values Added
Title Cross‑Origin StorageAccessAPI Data Leak Due to Insufficient Policy Enforcement
Type Values Removed Values Added
Title Cross‑Origin StorageAccessAPI Data Leak Due to Insufficient Policy Enforcement
Type Values Removed Values Added
Description Insufficient policy enforcement in StorageAccessAPI in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: Medium)
Weaknesses CWE-20
References
Weaknesses
  • CWE-20

    Improper Input Validation

Sources

Status
PUBLISHED
Assigner
Chrome
Published
Updated
Jul 1, 2026, 4:17 PM
Reserved
Jun 29, 2026, 11:04 PM
Status
Analyzed
Published
Jun 30, 2026, 11:17 PM
Modified
Oct 25, 2026, 9:10 PM