Security Resilience

CVE-2026-14151

Google Chrome ≤ 150.0.7871.47

Published
30 June 2026
Modified
01 July 2026
CVSS Score v3.1 8.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
EPSS Score 0.0033 25th percentile
Risk Priority 58 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-14151 is a high-severity Incorrect Resource Transfer Between Spheres (CWE-669) vulnerability in Google Chrome. Its CVSS base score is 8.3 (High).

Operationally, ranked at the 25th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

This vulnerability is AI-related — categorised as Other AI Platforms.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Inappropriate implementation in AI 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: Low)

CWE(s)

AI Security AnalysisAI

AI Category
Other AI Platforms
Risk Domain
N/A
OWASP Top 10 for LLMs 2025
None mapped
Classification Reason
Matched keywords: ai

Related Threats

CVEs Like This One

CVE-2025-12906Same product: Google Chrome
CVE-2023-0141Same product: Google Chrome
CVE-2026-19168Same product: Google Chrome
CVE-2026-17882Same product: Google Chrome
CVE-2023-0131Same product: Google Chrome
CVE-2026-13876Same product: Google Chrome
CVE-2026-17943Same product: Google Chrome
CVE-2026-17764Same product: Google Chrome
CVE-2026-17931Same product: Google Chrome
CVE-2026-19152Same product: Google Chrome

Affected Assets

google
chrome
≤ 150.0.7871.47

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

AC-3 directly requires enforcement of access authorizations via the protection mechanism itself.

AC-4 mandates use of information flow enforcement mechanisms to control data movement.

SC-2 requires separation of user and system functionality as a protection mechanism.

SC-28 requires protection mechanisms for information at rest.

SC-3 requires isolation of security functions from non-security functions.

SC-7 requires boundary protection mechanisms to monitor and control external communications.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

degrades

Information-transfer rules can prevent improper resource hand-off between spheres.

degrades

Access-control policies limit unintended control over transferred resources.

degrades

Managing access rights reduces risk of unauthorized resource transfer.

finds

Systematic verification that security mechanisms operate according to defined standards reduces the likelihood that protection mechanisms are bypassed or disabled.

degrades

Network-security controls can block improper cross-sphere transfers.

degrades

Network segregation directly limits unintended resource movement between spheres.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-669, a class-level weakness. Rules are authored against its narrower children: CWE-212, CWE-494, CWE-829.
  • No fine-grained STIG row for CWE-693, a pillar-level weakness. Rules are authored against its narrower children: CWE-654, CWE-757.

References