Loading vulnerability…
CVE-2026-8022 is a low-severity information disclosure vulnerability in Google Chrome’s MHTML handling affecting versions prior to 148.0.7778.96. The issue is described as an inappropriate implementation in MHTML that allows a remote attacker to use a crafted MHTML page to cause leakage of cross-origin data. Exploitation requires convincing a user to perform specific UI gestures while interacting with attacker-controlled content. The flaw does not indicate direct code execution; instead, it breaks expected origin isolation protections and exposes data that should remain inaccessible across origins.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An inappropriate implementation flaw in MHTML that could allow cross-origin data leakage via a crafted MHTML page with user interaction.
A low-severity inappropriate implementation flaw in Chrome's MHTML handling that could leak cross-origin data via a crafted MHTML page and user interaction.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.