Cyber Resilience

CVE-2026-11032

Google Chrome ≤ 149.0.7827.53

Published
04 June 2026
Modified
23 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:H/I:N/A:N
EPSS Score 0.0018 7th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-11032 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 Credentials from Web Browsers (T1555.003); 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-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 Password Manager in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to leak cross-origin data via a crafted HTML page. (Chromium security severity: Medium)

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1555.003 Credentials from Web Browsers Credential Access
Adversaries may acquire credentials from web browsers by reading files specific to the target browser.
Why these techniques?

Directly enables theft of stored browser credentials via cross-origin data leak in Password Manager.

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

CVEs Like This One

CVE-2026-7986Same product: Apple Macos
CVE-2026-11084Same product: Apple Macos
CVE-2026-11083Same product: Apple Macos
CVE-2026-9989Same product: Apple Macos
CVE-2026-13881Same product: Apple Macos
CVE-2026-11181Same product: Apple Macos
CVE-2026-11243Same product: Apple Macos
CVE-2026-11217Same product: Apple Macos
CVE-2026-12024Same product: Apple Macos
CVE-2026-11036Same product: Apple Macos

Affected Assets

google
chrome
≤ 149.0.7827.53

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • AC-4 Information Flow Enforcement
  • AC-3 Access Enforcement
  • SC-23 Session Authenticity
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

Enforces information flow policies that directly block unauthorized cross-origin data leakage from the Password Manager.

prevent

Enforces origin-based access decisions to stop crafted HTML pages from reading cross-origin password data.

prevent

Protects session authenticity to reduce the ability of malicious pages to obtain or misuse cross-origin credentials.

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