Cyber Resilience

CVE-2026-11270

CSRF in Google Chrome ≤ 149.0.7827.53

CSRF
Published
05 June 2026
Modified
17 June 2026
Patch / advisory
View 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.0019 9th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-11270 is a medium-severity CSRF (CWE-352) 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 9th 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 SI-2 (Flaw Remediation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A01:2025 Broken Access Control

EU & UK References

Vulnerability Data

Inappropriate implementation in UI in Google Chrome on Android prior to 149.0.7827.53 allowed a remote attacker to leak cross-origin data via a crafted HTML page. (Chromium security severity: Low)

CWE(s)
CWE-352

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?

Vulnerability in browser UI enables remote data leak via crafted HTML page, directly facilitating drive-by compromise attacks.

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

CVEs Like This One

CVE-2024-4128Same vendor: Google
CVE-2023-39412Same product: Google Android
CVE-2025-22343Shared CWE-352
CVE-2024-35010Shared CWE-352
CVE-2024-31612Shared CWE-352
CVE-2025-23513Shared CWE-352
CVE-2025-7684Shared CWE-352
CVE-2025-9882Shared CWE-352
CVE-2025-25166Shared CWE-352
CVE-2025-22325Shared CWE-352

Affected Assets

google
chrome
≤ 149.0.7827.53

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-2 Flaw Remediation
  • AC-4 Information Flow Enforcement
  • SC-23 Session Authenticity
Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V3.3.2
  • V3.5.1
  • V10.2.1

Mitigating Controls (NIST 800-53 r5) AI

SI-2 Flaw Remediation good match
prevent

Directly remediates the flawed UI implementation by requiring prompt application of the vendor fix for the cross-origin leak.

AC-4 Information Flow Enforcement good match
prevent

Enforces information flow rules that block unauthorized cross-origin data exposure attempted via the crafted HTML page.

SC-23 Session Authenticity partial match
prevent

Strengthens session authenticity mechanisms that reduce the effectiveness of CSRF-style cross-origin attacks described in CWE-352.

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 require anti-CSRF controls such as tokens or SameSite attributes.

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.23 Web filtering partial match
mitigates

By denying access to phishing or malicious sites, the control lowers the likelihood that a user will be tricked into submitting a forged request that performs an unintended action on another site.

A.5.7 Threat intelligence none match
none

Contextual intelligence about emerging CSRF toolkits can be translated into updated anti-CSRF token or same-site policy configurations across applications.

References