Loading vulnerability…
CVE-2026-87575 is an incorrect-authorization vulnerability in the Loader component of Google Chrome prior to version 153.0.8010.36. A remote attacker can use a crafted HTML page and social engineering to cause a user to interact with attacker-controlled content, bypassing system access restrictions. Chromium rates the vulnerability as Low severity.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This is a standalone eight-file Chrome exploit chain and Linux validation harness, not a framework module. stage1.js implements the CVE-2026-85046 V8 Float64Array corruption primitive, producing cage-relative 32-bit read/write and object-address primitives. poc.js builds custom WebAssembly modules, abuses exception handling/forged getters to extend the primitive, discovers renderer code aliases, and writes embedded x86-64 code that changes memory protections and patches memcpy GOT entries, reporting FULL_RW on success. retarget-loader.js dynamically fetches and instruments poc.js, then creates a sandboxed iframe targeting /STAGE2_C. After renderer-stage completion it enables a user-facing button. retarget-receiver.js receives the iframe message and assigns its source window to a mailto URI, attempting to carry/misattribute the user activation and invoke Evolution externally. run.py serves the stages on an ephemeral localhost port, launches specific vulnerable/fixed Chrome artifact versions via Selenium, monitors /proc and process activity for xdg-open/Evolution, and compares vulnerable versus fixed behavior. The payload is operational but heavily version-specific and uses hard-coded layout assumptions, addresses, native code, and external-handler expectations.
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.
An incorrect-authorization vulnerability in the Google Chrome Loader component that can allow a remote, socially engineered attacker to bypass system access restrictions using a crafted HTML page. It affects Chrome versions prior to 153.0.8010.36 and is rated Low severity by Chromium.
A network-reachable vulnerability requiring user interaction that can cause limited integrity impact. The content identifies Debian Linux 12.0, 13.0, and 14.0 and references Chromium in CPE data, but does not otherwise describe the underlying flaw.
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.