CriticalCVE-2025-6205

    Missing authorization vulnerability affecting DELMIA Apriso from Release 2020 through Release 2025 (CVE-2025-6205)

    Published In CISA KEV since Sources: CVE.org, pwn.watch

    What is affected, what to do

    A missing authorization vulnerability affecting DELMIA Apriso from Release 2020 through Release 2025 could allow an attacker to gain privileged access to the application.

    The vulnerability is being actively exploited; treat it as a priority. Update delmia_apriso to version 2025. 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..*

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    9.1

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    9.1

    CVSS v3

    Severity Critical on the scale from 0 to 10.

    Source: CVE.org, pwn.watch

    73.7 %

    EPSS score

    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.

    Source: FIRST EPSS, percentile 99.47

    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.82 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.1 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.1
    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
    73.7 %
    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.47
    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 · automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 28 October 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-862

    Response and mitigation

    Why act now?

    Prioritisation rationale

    This flaw is exploitable over the network without authentication or user interaction and hands an attacker privileged access to an MES that holds work orders, recipes, quality data and interfaces to ERP and the control layer — confidentiality and integrity of production data are fully at stake. Its exploitation likelihood is among the very highest of any CVE, and typical targets are manufacturers in automotive, aerospace, pharma and consumer goods, where Apriso often spans multiple plants and is sometimes reachable via partner networks. CISA does not flag ransomware use, but a compromised MES is an ideal foothold for sabotage, espionage and later extortion. For KRITIS and NIS2 entities running Apriso, treat this as critical: wall off any instance reachable from outside the MES zone within 24 hours and patch within days; strictly segmented internal instances remain high priority for the next maintenance window.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Inventory: Identify every DELMIA Apriso instance (Release 2020 through 2025, including test, training and plant-level systems) with release, hotfix level and reachability (internet, partner VPN, corporate LAN, OT DMZ). Instances whose IIS web portal or web services are reachable from outside the production network come first.
      • Patch: Per the CVE data the issue is fixed in the 2025 updates. Patch available from the vendor — look up the exact version and hotfix identifier in the Dassault Systèmes security advisory or the 3DS support portal. Request the fix for each affected Golden Release and agree an emergency maintenance window with plant management and MES operations.
      • Cut exposure now: If you cannot patch immediately, firewall the Apriso web application (typically HTTP/HTTPS on TCP 80/443 via IIS) down to defined source networks — shop-floor clients, jump hosts, integration servers. Remove any direct internet exposure and broad corporate-LAN access.
      • Start a compromise assessment: Review the user and role tables in the Apriso database (SQL Server/Oracle) for accounts created or elevated to administrative roles since July 2025. Disable suspicious accounts — don't delete them, preserve evidence.
      • Rotate credentials: On any indication of access, rotate passwords for privileged Apriso application accounts, the database service account, the IIS app-pool identity and credentials for connected interfaces (ERP/SAP integration, SCADA/historian connectors).
      • Preserve evidence: Collect IIS logs, Apriso application logs and database audit data before rotating; snapshot the servers before patching.
    2. Runbook step 2

      Mitigation layers

      • Network segmentation (IEC 62443 / Purdue): Place Apriso servers in a dedicated MES zone (Level 3) between IT and OT. Allow IT (Level 4/5) access only via reverse proxy or jump host; block all inbound internet traffic. Default-deny egress from the Apriso servers, allowing only known destinations (database, ERP, licence server).
      • Reverse proxy / WAF: Publish the Apriso web application only behind an authenticating reverse proxy (pre-authentication via SAML/OIDC with MFA) so unauthenticated requests never reach the application. Restrict administrative paths and web-service endpoints to an IP allow-list of admin hosts.
      • IAM / least privilege: Cut administrative Apriso roles to the minimum and reconcile role assignments against an approved baseline. Run the IIS app-pool identity and DB service account without local admin and without sysadmin/db_owner where the vendor supports it.
      • Endpoint hardening: Enable EDR on Apriso servers and block shell processes spawned by w3wp.exe (ASR rule or AppLocker/WDAC policy for cmd.exe, powershell.exe, certutil.exe) where operations allow — run in audit mode first.
      • Database auditing: Enable SQL Server Audit (or Oracle Unified Auditing) for INSERT/UPDATE on user, role and permission tables in the Apriso database and forward to the SIEM.
      • Third-party access: Until patched, move integrator and Dassault partner remote access to time-boxed, recorded sessions.
    3. Runbook step 3

      Detection rules

      • IIS access logs (W3C): Requests to administrative pages or web-service endpoints of the Apriso application returning HTTP 200 without a prior successful login from the same source IP or without a session cookie, especially from IPs outside shop-floor/admin ranges. SPL sketch: index=iis host=apriso* sc_status=200 NOT [| inputlookup apriso_allowed_src.csv] | stats count values(cs_uri_stem) by c_ip
      • Application/database: New or modified accounts with administrative roles outside change management; role changes by accounts that don't normally administer. Sigma shape: logsource: database / selection: table|contains: ['User','Role','Permission'] action: ['INSERT','UPDATE'] / filter: user in approved_admins
      • Sysmon EID 1 / EDR process ancestry: w3wp.exe (Apriso app pool) spawning cmd.exe, powershell.exe, rundll32.exe, certutil.exe or whoami.exe — follow-on abuse of privileged access. KQL: DeviceProcessEvents | where InitiatingProcessFileName =~ "w3wp.exe" and FileName in~ ("cmd.exe","powershell.exe","certutil.exe","whoami.exe")
      • Sysmon EID 11 / file integrity: New .aspx, .ashx or .dll files in the Apriso web directory or IIS root outside maintenance windows (webshell indicator).
      • Network (Zeek/Suricata): Outbound connections from Apriso servers to unknown external hosts, or unusual connections from the MES zone into OT networks (Level 1/2) — signs of lateral movement toward production.

    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 missing authorization vulnerability affecting DELMIA Apriso from Release 2020 through Release 2025 could allow an attacker to gain privileged access to the application.

    Source: NVD (NIST), CISA KEV Catalog, CVE.org (MITRE), cvelistv5, pwn.watch

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    Dassault SystèmesDELMIA Apriso
    • ≥ Release 2021 Golden
    • ≥ Release 2020 Golden
    • ≥ Release 2022 Golden
    • ≥ Release 2024 Golden
    • ≥ Release 2025 Golden
    • ≥ Release 2023 Golden
    • —
    • —
    • —
    • —
    • —
    • —
    3dsdelmia_apriso
    • 2020 – < 2025
    • 2025

    Vendors and products

    Weakness classes (CWE)

    • CWE-862Missing Authorization

      Class

      The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

      Entry at MITRE CWE-862

    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.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited

    References & sources

    • 3ds.comDassault Systèmes advisory: Dassault Systèmes DELMIA AprisoVendor advisory, pwn-watch
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2025-6205government-resource, US government resource
    • pwn.watchpwn.watch: Dassault Systèmes DELMIA Apriso: 2 exploited vulnerabilities (CVE-2025-6204, CVE-2025-6205)pwn-watch
    • 3ds.comDassault Systèmes advisory: Dassault Systèmes DELMIA Aprisopwn-watch
    • NVD (NIST)NVD: CVE-2025-6204pwn-watch
    • NVD (NIST)NVD: CVE-2025-6205pwn-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.

    Badge preview for CVE-2025-6205
    <a href="https://intel.neosec.eu/en/cve/CVE-2025-6205"><img src="https://intel.neosec.eu/badge/cve/CVE-2025-6205.svg?lang=en" alt="CVE-2025-6205 – NEOSEC Intel" height="20"></a>