Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Back to vulnerabilities
Low

Cross-origin data leak in Google Chrome MHTML

IdentifiersCVE-2026-8022CWE-200

CVE-2026-8022 is a low-severity inappropriate implementation flaw in the MHTML component of Google Chrome affecting versions prior to 148.0.7778.96. A remote attacker can use a crafted MHTML page to cause leakage of cross-origin data if they can convince a user to perform specific UI gestures. Based on the available information, the issue is an implementation error in Chrome's handling of MHTML content that results in unintended exposure of data across origin boundaries, rather than memory corruption or code execution.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial
ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows disclosure of cross-origin data that should normally be protected by browser origin isolation controls. The impact is limited to information leakage; the provided information does not indicate arbitrary code execution, privilege escalation, or sandbox escape. Exploitation requires user interaction and was rated Low severity by Chromium.

Mitigation

If you can’t patch tonight, do this now.

Until patched versions are deployed, reduce exposure by avoiding opening untrusted or unsolicited MHTML content, restricting delivery of attacker-controlled MHTML files/pages, and training users not to perform unexpected browser UI gestures prompted by untrusted content. Enterprise environments may also limit or disable workflows involving MHTML where operationally feasible.

Remediation

Patch, then assume compromise.

Update Google Chrome to version 148.0.7778.96 or later on affected platforms. Because the issue affects Chromium, corresponding updates should also be applied to Chromium-based browsers and enterprise Chromium deployments once vendor fixes are available.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GoogleChromeapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

4 SOURCESView more in app
What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Start free trial
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity1

Community discussion across Reddit, Mastodon, and other social sources.

EXTERNAL REFERENCES
MITRE CVE
cve.org · CVE-2026-8022
NVD
nvd.nist.gov/vuln/detail/CVE-2026-8022
MITRE CWE · CWE-200
cwe.mitre.org
Vendor Advisory
chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop.html
Permissions Required
issues.chromium.org/issues/499194407