Cyber Resilience

CVE-2026-15775

Google Chrome ≤ 150.0.7871.125

Published
14 July 2026
Modified
15 July 2026
Patch / advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
EPSS Score 0.0022 13th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-15775 is a medium-severity Origin Validation Error (CWE-346) vulnerability in Google Chrome. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Drive-by Compromise (T1189); ranked at the 13th 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-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 V8 in Google Chrome prior to 150.0.7871.125 allowed a remote attacker to bypass same origin policy via a crafted HTML page. (Chromium security severity: High)

CWE(s)

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.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
Why these techniques?

SOP bypass via crafted HTML page directly enables drive-by compromise (T1189) and client application exploitation for execution (T1203).

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

CVEs Like This One

CVE-2026-13838Same product: Google Chrome
CVE-2026-14057Same product: Google Chrome
CVE-2026-14105Same product: Google Chrome
CVE-2026-14079Same product: Google Chrome
CVE-2026-15768Same product: Google Chrome
CVE-2026-14039Same product: Google Chrome
CVE-2026-13839Same product: Google Chrome
CVE-2025-2135Same product: Google Chrome
CVE-2026-6363Same product: Google Chrome
CVE-2026-14054Same product: Google Chrome

Affected Assets

google
chrome
≤ 150.0.7871.125

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • AC-3 Access Enforcement
  • AC-4 Information Flow Enforcement
  • SC-46 Cross Domain Policy Enforcement
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 3 hardening rules · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly enforces same-origin policy access decisions to block unauthorized cross-origin interactions attempted by the crafted HTML page.

prevent

Enforces information flow rules between security domains (origins) to stop the V8 implementation flaw from allowing cross-origin data access.

prevent

Provides cross-domain policy enforcement mechanisms that can mitigate same-origin policy bypasses at the browser boundary.

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.AA-03 mostly match
prevents

Authentication directly verifies the source of users/services/hardware, mitigating origin validation failures.

PR.AA-04 mostly match
prevents

Verifying identity assertions enforces origin validation for conveyed claims.

ID.AM-03 partial match
prevents

Documenting authorized flows supports origin validation by defining expected sources.

PR.IR-01 partial match
prevents

Protecting networks from unauthorized access requires origin checks on communication sources.

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.

mitigates

Network security controls enforce origin validation at network boundaries.

mitigates

Security of network services includes validating the authenticity of service endpoints.

mitigates

Network segregation reduces exposure but does not directly validate origins.

prevents

Application security requirements explicitly call for origin validation of inputs and communications.

prevents

Secure architecture principles encourage origin checks but do not mandate them.

prevents

Secure coding practices include implementing proper origin validation to prevent spoofing.

References