CVE-2026-106413 is a race condition in the Browser component of Google Chrome before version 155.0.8059.39. A remote attacker who has already compromised the renderer process can use a crafted HTML page to spoof browser user-interface elements. The vulnerability does not itself establish an initial renderer-compromise mechanism.
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.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A browser race condition affecting Google Chrome before version 155.0.8059.39 permits UI spoofing through crafted HTML after an attacker has compromised the renderer process. The Nessus plugin identifies affected Debian Chromium packages as vendor-unpatched and reports no known solution. Severity assessments differ: Chromium rates the flaw Low, while the plugin lists a Critical CVSS v3 score of 9.8.
A race condition in Google Chrome versions before 155.0.8059.39 allows a remote attacker with an already-compromised renderer process to spoof UI elements using a crafted HTML page. Chromium rates the vulnerability as Low severity.
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.