CVE-2026-9110 is a critical inappropriate implementation vulnerability in the Google Chrome UI layer on Windows affecting versions prior to 148.0.7778.179. The flaw allows a remote attacker, after first compromising the renderer process, to use a crafted HTML page to spoof browser interface elements. The issue is rooted in incorrect handling or presentation of trusted browser UI, enabling attacker-controlled content to be displayed in a way that can appear legitimate to the user and undermine browser security boundaries.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical Chrome UI spoofing vulnerability on Windows that allows an attacker with a compromised renderer process to display convincing fake browser windows or dialogs via a crafted HTML page.
A critical inappropriate implementation flaw in the Chrome UI layer that could enable security restriction bypass or browser interface spoofing.
A critical inappropriate implementation vulnerability in the Chrome UI.
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.