Loading vulnerability…
A stored cross-site scripting (XSS) vulnerability in Altium Workflow Engine is caused by missing server-side input sanitization in workflow form submission APIs. An authenticated, non-administrative user can submit workflow form data containing arbitrary JavaScript that is persisted in workflow records. When an administrator later views the affected workflow in the administrative UI, the injected script executes in the administrator’s browser context, enabling attacker-controlled actions within the admin session.
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.
Repository is a small Python proof-of-concept for CVE-2026-1010, demonstrating WebSocket connection smuggling caused by inconsistent parsing between a reverse proxy and a backend. It contains three code files: (1) reverse_proxy.py, a minimal forwarding proxy on port 8080 that relays GET requests to http://localhost:8081; (2) websocket_backend.py, a deliberately vulnerable backend on port 8081 that switches behavior when it sees 'Upgrade: websocket', performs a simplistic WebSocket handshake, reads a few bytes, and then writes an HTTP-like response; and (3) exploit_ws_smuggling.py, which opens a raw socket to 127.0.0.1:8080 and sends a crafted request containing a normal-looking WebSocket upgrade followed by a second hidden 'GET /admin' request. The exploit capability is request/connection smuggling leading to potential access control bypass or cache poisoning in front-end/back-end chains that disagree on request boundaries. This is a real exploit demonstration rather than a detector, but it is a lab-style POC with a hardcoded payload and local demo topology rather than a generalized weaponized exploit.
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.
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.