Dassault Systèmes DELMIA Apriso Deserialization of Untrusted Data Vulnerability (CVE-2025-5086)
Published In CISA KEV since Sources: pwn.watch, CVE.org
What is affected, what to do
A deserialization of untrusted data vulnerability affecting DELMIA Apriso from Release 2020 through Release 2025 could lead to a remote code execution.
The vulnerability is being actively exploited; treat it as a priority. The available sources name no fixed version. Check the vendor guidance in the references below. Immediate actions, mitigation and detection rules are in the runbook below.
- Affected
- Dassault Systèmes DELMIA Apriso
gte Release 2020 Golden..* - Dassault Systèmes DELMIA Apriso
gte Release 2021 Golden..* - Dassault Systèmes DELMIA Apriso
gte Release 2022 Golden..* - Dassault Systèmes DELMIA Apriso
gte Release 2023 Golden..* - Dassault Systèmes DELMIA Apriso
gte Release 2024 Golden..* - Dassault Systèmes DELMIA Apriso
gte Release 2025 Golden..*
- Dassault Systèmes DELMIA Apriso
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
9.0
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: NVD, CVSS v3
9.0
CVSS v3
Severity Critical on the scale from 0 to 10.
Source: pwn.watch, CVE.org
97.0 %
EPSS score
High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
Source: FIRST EPSS, percentile 99.89
Show all metrics
- Severity
- Critical
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 234.04 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- actively exploitedSource: VulnCheck KEV (opens in a new tab) How we classify
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 9.0 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 9.0
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 97.0 %
- High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 99.89
- Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- Actively exploited
- Published
In CISA KEV since
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- CISA assessment (SSVC)
- Exploitation: active · not automatable · Technical impact: total
- Source: CISA Vulnrichment, as of 12 September 2025
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-502
Response and mitigation
Why act now?
Prioritisation rationale
This CVE sits on KEV because unauthenticated deserialisation in a .NET-based MES platform yields direct RCE under the service account — a textbook ysoserial-class flaw, weaponised within days of disclosure and sitting among the CVEs most likely to be exploited according to EPSS. DELMIA Apriso drives production lines in automotive, aerospace and pharma; a compromised Apriso server is a pivot into OT and can tamper with production logic, exfiltrate recipes or halt lines — squarely NIS2/KRITIS-relevant even without a confirmed ransomware campaign. Treat as P1/critical for any organisation where Apriso is reachable from anything beyond a narrow OT admin network; with strict air-gapped segmentation it can be P2 with a 14-day patch deadline.
Runbook step 1
Immediate response (0-24 h)
- Deploy the Dassault Systèmes patch for DELMIA Apriso Release 2020–2025. Pull the exact hotfix/service-pack designation from the vendor advisory on the 3DEXPERIENCE support portal — a vendor fix was flagged when the CVE hit KEV; confirm the latest Golden release plus security rollup.
- Pull every Apriso web/application server (typically IIS hosting Apriso web services on ports 80/443, sometimes 8080) off the internet immediately; permit access only through VPN or a reverse proxy with mutual TLS until the patch lands.
- Hunt the Apriso IIS worker (w3wp.exe in the Apriso AppPool, Apriso service accounts) for anomalous child processes in recent weeks (cmd.exe, powershell.exe, rundll32.exe). Any hit → trigger IR, isolate the host.
- Rotate all Apriso service credentials (database user, AD service account, API keys to MES/ERP integrations); assume full account compromise once RCE is on the table.
- Capture a forensic snapshot of affected servers before patching or rolling back — manufacturing IT rarely has backup retention long enough to preserve attacker artefacts.
- Notify CSIRT, plant management and, where applicable, the national NIS2 competent authority (24 h early-warning window) given the production-outage risk.
Runbook step 2
Mitigation layers
- Network segmentation: keep Apriso servers strictly inside the OT/MES zone (Purdue Level 3); no direct internet egress, no east-west reachability from office VLANs except via defined jump hosts.
- WAF/reverse proxy in front of Apriso endpoints: block SOAP/.NET remoting requests with suspicious content-types (application/octet-stream, text/xml carrying SoapFormatter/BinaryFormatter payload signatures) and oversized Base64 blobs in request bodies. Enforce a request-size cap.
- IIS AppPool hardening: run the Apriso pool as a dedicated low-privilege service account; apply an AppLocker/WDAC policy that denies cmd.exe, powershell.exe, bitsadmin, certutil, mshta spawning from the w3wp process tree.
- Egress filtering from the Apriso host: allowlist only DB, AD, SMTP, licence server; drop and alert on any outbound HTTP(S) to non-allowlisted destinations at the firewall.
- EDR with an explicit "deserialisation RCE" behavioural rule: w3wp.exe → script/LOLBin child, with auto-kill.
- Keep Apriso DB and configuration backups offline; rehearse restore — a production halt costs more than the breach itself.
Runbook step 3
Detection rules
- Sysmon EID 1 (Process Create) where ParentImage endswith
w3wp.exeand CommandLine contains the Apriso AppPool path, Child incmd.exe|powershell.exe|rundll32.exe|regsvr32.exe|mshta.exe|certutil.exe→ high-severity alert. - IIS access logs (W3C) for POST requests to Apriso web-service URIs with abnormally large content-lengths (>50 KB) and HTTP 500/200 response patterns diverging from the baseline; KQL shape:
W3CIISLog | where csUriStem has "Apriso" and csMethod == "POST" and scStatus in (200,500) | summarize count() by cIP, bin(TimeGenerated,1h) | where count_ > 20. - Sysmon EID 11/15 for file writes by w3wp.exe outside Apriso install directories, especially into
C:\Windows\Temp,C:\ProgramData,C:\Users\Public— classic webshell/loader drop paths. - Windows Security EID 4624/4672 for the Apriso service account from unusual source hosts or at atypical hours; alert on Logon Type 3 outside the known server peer set.
- Network (Zeek/Suricata): new outbound flows from the Apriso host to cloud storage, Pastebin clones, non-routed external IPs; Suricata idea: alert on TLS SNI not in the allowlist of known MES/ERP peers.
- Sysmon EID 1 (Process Create) where ParentImage endswith
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
A deserialization of untrusted data vulnerability affecting DELMIA Apriso from Release 2020 through Release 2025 could lead to a remote code execution.
Source: pwn.watch, cvelistv5, NVD (NIST), CISA KEV Catalog, CVE.org (MITRE)
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| Dassault Systèmes | DELMIA Apriso |
|
|
| 3ds | delmia_apriso |
|
|
Vendors and products
Weakness classes (CWE)
CWE-502Deserialization of Untrusted Data
Base
The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
Entry at MITRE CWE-502
Public exploit references
Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.
| CISA KEV Catalog | CISA Known Exploited Vulnerability (opens in a new tab)cisa.gov | actively exploited |
References & sources
- 3ds.comvulnerability/advisoriesVendor advisory
- isc.sans.edudiary/Exploit+Attempts+for+Dassault+DELMIA+Apriso+CVE20255086/3…media-coverage, Exploit, Technical description, Third-party advisory
- cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2025-5086government-resource, US government resource
- pwn.watchpwn.watch: Dassault Systèmes DELMIA Apriso: DELMIA Apriso Deserialization of Untrusted Data Vulnerabilitypwn-watch
- 3ds.comDassault Systèmes advisory: Dassault Systèmes DELMIA Aprisopwn-watch
- NVD (NIST)NVD: CVE-2025-5086pwn-watch
- cisa.govCISA Known Exploited Vulnerabilities Catalogpwn-watch
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2025-5086"><img src="https://intel.neosec.eu/badge/cve/CVE-2025-5086.svg?lang=en" alt="CVE-2025-5086 – NEOSEC Intel" height="20"></a>