CVE-2026-8022

Analyzed Analyzed - Analysis Complete

Inappropriate MHTML Implementation in Google Chrome Leads to Cross-Origin Data Leak

Publication date: 2026-05-06

Last updated on: 2026-05-07

Assigner: Chrome

Description

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)

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-05-06

Last Modified

2026-05-07

Generated

2026-07-06

AI Q&A

2026-05-06

EPSS Evaluated

2026-07-05

NVD

CVE-2026-8022

EUVD

EUVD-2026-28147

Affected Vendors & Products

Vendor	Product	Version / Range
google	chrome	to 148.0.7778.96 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-352	The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
CWE-1021	The web application does not restrict or incorrectly restricts frame objects or UI layers that belong to another application or domain, which can lead to user confusion about which interface the user is interacting with.

Attack-Flow Graph

Executive Summary

This vulnerability is an inappropriate implementation in the MHTML feature of Google Chrome versions prior to 148.0.7778.96. It allows a remote attacker to leak cross-origin data by convincing a user to perform specific user interface gestures on a specially crafted MHTML page.

Impact Analysis

The impact of this vulnerability is that an attacker could potentially access data from other origins (websites) that should be isolated, leading to unauthorized data leakage. This could compromise user privacy and security by exposing sensitive information through crafted MHTML content.

Mitigation Strategies

To mitigate this vulnerability, update Google Chrome to version 148.0.7778.96 or later, as the issue is fixed in that release.

Additionally, avoid interacting with untrusted MHTML pages or links that could trigger the vulnerability.

Hi! I’m here to help you understand CVE-2026-8022. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70