Cyber Resilience

CVE-2026-8022

CSRF in Google Chrome ≤ 148.0.7778.96

CSRF
Published
06 May 2026
Modified
17 June 2026
Patch / advisory
View advisory
CVSS Score v3.1 3.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
EPSS Score 0.0015 5th percentile
Risk Priority 26 floored blend · peak EPSS

Summary

CVE-2026-8022 is a low-severity CSRF (CWE-352) vulnerability in Google Chrome. Its CVSS base score is 3.1 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Drive-by Compromise (T1189); ranked at the 5th 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 SC-23 (Session Authenticity) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A01:2025 Broken Access ControlA06:2025 Insecure Design

EU & UK References

Vulnerability Data

Inappropriate implementation in MHTML in Google Chrome prior to 148.0.7778.96 allowed a remote attacker who convinced a user to engage in specific UI gestures to leak cross-origin data via a crafted MHTML page. (Chromium security severity: Low)

CWE(s)
CWE-352CWE-1021

Related Threats

MITRE ATT&CK Enterprise Techniques

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 →
T1056 Input Capture Collection
Adversaries may use methods of capturing user input to obtain credentials or collect information.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1557 Adversary-in-the-Middle Credential Access
Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as [Network Sniffing](https://attack.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-14373Same product: Apple Macos
CVE-2025-6557Same product: Google Chrome
CVE-2024-49779Same product: Linux Linux Kernel
CVE-2023-44160Same product: Linux Linux Kernel
CVE-2025-52841Same product: Apple Macos
CVE-2024-25692Same product: Linux Linux Kernel
CVE-2023-44161Same product: Linux Linux Kernel
CVE-2025-1923Same product: Google Chrome
CVE-2023-7013Same product: Google Chrome
CVE-2024-40817Same product: Apple Macos

Affected Assets

google
chrome
≤ 148.0.7778.96

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

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

AC-3 Access Enforcement partial match

Access enforcement requires verifying that state-changing requests originate from the authenticated user rather than a forged cross-site source.

SC-23 Session Authenticity partial match

Protecting session authenticity prevents attackers from replaying or forging authenticated requests via the victim's browser.

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.29 Security testing in development and acceptance mostly match
finds

Security testing can detect missing frame protections, but does not itself implement 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.8.26 Application security requirements partial match
prevents

Application security requirements can mandate frame-ancestors / X-Frame-Options, directly addressing UI redressing risks.

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

Secure architecture principles include isolation of UI layers and proper use of browser security controls.

A.8.28 Secure coding partial match
prevents

Secure coding practices directly require implementation of frame-busting headers or CSP frame-ancestors directives.

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