Loading vulnerability…
CVE-2026-42099 is a race condition in Sparx Pro Cloud Server, specifically in WebEA's /data_api/dl_internal_artifact.php endpoint. The endpoint downloads properties of the object referenced by the guid parameter and writes the retrieved content to the application's current directory (DIR) using an attacker-controlled filename. An attacker with repository access can control both the filename and file contents, allowing creation of a malicious PHP file in a web-accessible location. Although the application deletes the file after processing, a timing window exists while the response is still being transmitted. By delaying transmission, for example with a large file or a slow client connection, the attacker can keep the temporary PHP file accessible long enough to issue a second request to that file and execute it. Public reporting states this was confirmed on Sparx Pro Cloud Server 6.1 build 167 and below; other versions were not tested and may also be affected.
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.
4 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.