Loading vulnerability…
CVE-2026-106255 is a race condition in the V8 engine affecting Google Chrome versions before 155.0.8059.39. A remote attacker can potentially trigger the vulnerability through a crafted HTML page to execute arbitrary code inside the browser sandbox. The specific vulnerable function and race-triggering sequence are not identified.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity V8 race condition affecting Google Chrome versions before 155.0.8059.39 could allow remote code execution inside the browser sandbox through a crafted HTML page. The Nessus advisory identifies affected Debian chromium packages as vendor-unpatched and states that no known solution exists. The reported CVSS v3 base score is 8.8; successful exploitation requires user interaction.
A high-severity race condition in Chrome's V8 engine affecting versions before 155.0.8059.39. A remote attacker could potentially execute arbitrary code within the sandbox through a crafted HTML page; sandbox escape is not described.
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.