Cyber Resilience

CVE-2026-15130

Google Chrome ≤ 150.0.7871.115

Published
08 July 2026
Modified
09 July 2026
Patch / advisory
View advisory
CVSS Score v3.1 4.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
EPSS Score 0.0017 7th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-15130 is a medium-severity Client-Side Enforcement of Server-Side Security (CWE-602) vulnerability in Google Chrome. Its CVSS base score is 4.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Drive-by Compromise (T1189); ranked at the 7th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

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

OWASP Top 10 for Web (2025)

A06:2025 Insecure Design

EU & UK References

Vulnerability Data

Insufficient policy enforcement in Navigation in Google Chrome prior to 150.0.7871.115 allowed a remote attacker to bypass site isolation via a crafted HTML page. (Chromium security severity: High)

CWE(s)
CWE-602

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1189 Drive-by Compromise Initial Access
Adversaries may gain access to a system through a user visiting a website over the normal course of browsing.
attack.mitre.org →
Why these techniques?

The vulnerability allows bypassing site isolation via crafted HTML, which aligns with Drive-by Compromise (T1189) where an attacker delivers malicious content through a web page to compromise the browser sandbox.

Confidence: MEDIUM · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-13930Same product: Google Chrome
CVE-2026-14054Same product: Google Chrome
CVE-2026-14086Same product: Google Chrome
CVE-2026-14007Same product: Google Chrome
CVE-2026-14105Same product: Google Chrome
CVE-2026-13818Same product: Google Chrome
CVE-2026-13893Same product: Google Chrome
CVE-2026-13984Same product: Google Chrome
CVE-2026-9908Same product: Google Chrome
CVE-2026-13790Same product: Google Chrome

Affected Assets

google
chrome
≤ 150.0.7871.115

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SC-7 Boundary Protection
  • AC-4 Information Flow Enforcement
  • SC-2 Separation of System and User Functionality
Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V10.7.1
  • V2.2.2
  • V8.3.1
  • V10.4.1

Mitigating Controls (NIST 800-53 r5) AI

SC-7 Boundary Protection good match
prevent

Boundary protection mechanisms such as site isolation directly block the unauthorized cross-origin navigation that the crafted HTML page exploits.

AC-4 Information Flow Enforcement good match
prevent

Information flow enforcement policies can be configured to enforce the same-origin and site-isolation rules that the vulnerability bypasses.

SC-2 Separation of System and User Functionality partial match
prevent

Separating system/user or renderer processes limits the impact of a bypassed site-isolation policy, reducing the attack surface.

Mitigating Controls (NIST CSF 2.0) AI

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

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent design flaws that place server security enforcement on the client.

PR.AA-05 partial match
prevents

Proper policy-based enforcement of authorizations implies server-side controls rather than client-only checks.

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.

A.8.27 Secure system architecture and engineering principles mostly match
prevents

Secure architecture principles discourage client-side trust but do not directly address this weakness.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing can detect client-side enforcement but is not the primary mitigation.

A.8.3 Information access restriction mostly match
prevents

Information access restriction is undermined when the client is trusted to enforce it.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates server-side validation and prevents reliance on client enforcement.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for server-side enforcement of security mechanisms.

A.8.28 Secure coding partial match
prevents

Secure coding standards require server-side checks and reject client-only enforcement.

References