Loading vulnerability…
CVE-2026-25586 is a sandbox escape vulnerability in SandboxJS affecting versions prior to 0.8.29. The flaw arises from property-access logic that relies on hasOwnProperty checks on sandboxed objects to enforce a prototype whitelist. An attacker can shadow or replace hasOwnProperty on a sandbox object so that the check incorrectly reports success, causing whitelist enforcement in the property-access path to be skipped. This allows access to blocked prototype properties, including proto, and enables modification of the host Object.prototype. Because the polluted prototype state can affect subsequent executions, the issue can produce persistent cross-sandbox impact and undermine the isolation guarantees of the library.
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.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.