Skip to content
CTI Academy Sponsor CTI Academy
CRITICAL · CVSS 9 CISA Known Exploited Vulnerability

CVE-2025-5086

Dassault Systèmes DELMIA Apriso Deserialization of Untrusted Data Vulnerability

Dassault Systèmes DELMIA Apriso

A deserialization of untrusted data vulnerability affecting DELMIA Apriso from Release 2020 through Release 2025 could lead to a remote code execution.

CVSS
9
CRITICAL
EPSS
97.1%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
2 Jun 2025
CWE-502

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 11 September 2025. US federal agencies were required to remediate it by 2 October 2025.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 97.1%, which is higher than 99.9% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

Frequently asked questions

Is CVE-2025-5086 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2025-5086.

What does CVE-2025-5086 affect?

CVE-2025-5086 affects Dassault Systèmes DELMIA Apriso. A deserialization of untrusted data vulnerability affecting DELMIA Apriso from Release 2020 through Release 2025 could lead to a remote code execution.

How severe is CVE-2025-5086?

CVE-2025-5086 is rated CRITICAL with a CVSS base score of 9. EPSS puts the probability of exploitation in the next 30 days at 97.1%, higher than 99.9% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 2 October 2025.

How should organisations respond to CVE-2025-5086?

Apply the vendor patch for Dassault Systèmes DELMIA Apriso as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.