Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
CriticalCISA KEVExploited in the wildPublic exploit

Remote Code Execution in Dassault Systèmes DELMIA Apriso via Deserialization of Untrusted Data

IdentifiersCVE-2025-5086CWE-502· Deserialization of Untrusted Data

CVE-2025-5086 is a critical deserialization of untrusted data vulnerability in Dassault Systèmes DELMIA Apriso. It affects DELMIA Apriso Release 2020 through Release 2025, including versions up to and including 2020 SP4, 2021 SP3, 2022 SP3, 2023 SP3, 2024 SP1, and 2025 SP1. The flaw is remotely reachable over the network and, according to vendor and downstream reporting, can be exploited without authentication or user interaction to achieve remote code execution on the vulnerable host. Public reporting does not identify the specific vulnerable function or code path, but the issue is consistently described as unsafe deserialization of attacker-controlled data within the Apriso application. CISA added the vulnerability to the KEV catalog, and multiple reports state there is evidence of active exploitation in the wild.

Share:
For your environment

Are you exposed to this one?

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.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can allow arbitrary code execution on the DELMIA Apriso host and may result in full system compromise. Because Apriso is used in manufacturing operations management and can interface with factory equipment and ERP systems, compromise can expose sensitive operational and business data, enable malware deployment, espionage, keylogging and screenshot capture via follow-on payloads, disrupt production workflows, create supply-chain impacts, and potentially contribute to equipment or process failures. Confidentiality, integrity, and availability impact are all high.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by restricting network access to DELMIA Apriso to trusted management and application paths only, removing any unnecessary internet exposure, and segmenting Apriso systems from broader enterprise and OT networks. Apply compensating controls such as WAF or reverse-proxy filtering where feasible, monitor for suspicious requests consistent with deserialization exploitation, and hunt for indicators of compromise including unexpected DLL or executable downloads and execution on Apriso hosts. Because exploitation has been associated with delivery of malicious payloads, perform host-based review for persistence, spyware activity, and anomalous child processes spawned by the application.

Remediation

Patch, then assume compromise.

Upgrade DELMIA Apriso to the latest vendor-provided security patch level from Dassault Systèmes. The vulnerable ranges include Release 2020 through 2025 up to and including 2020 SP4, 2021 SP3, 2022 SP3, 2023 SP3, 2024 SP1, and 2025 SP1; organizations should move to the fixed versions made available by the vendor in June 2025 or later. Given confirmed in-the-wild exploitation and KEV inclusion, remediation should be prioritized on an emergency basis, especially for internet-reachable or externally accessible Apriso deployments.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
3dsDelmia Aprisoapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware2

Malware families riding this exploit, with evidence and IOCs.

Detection signatures3

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity55

Community discussion across Reddit, Mastodon, and other social sources.