Dassault 3DEXPERIENCE Flaw CVE-2026-93664 Allows CVSS 10.0 RCE

Dassault Systemes disclosed three critical 3DEXPERIENCE Station Launcher flaws, including CVE-2026-93664, a CVSS 10.0 unauthenticated RCE deserialization bug.
Table of Contents
    Add a header to begin generating the table of contents

    Dassault Systemes has disclosed three critical vulnerabilities in the Station Launcher App of its 3DEXPERIENCE platform, led by CVE-2026-93664, a deserialization flaw that allows unauthenticated remote code execution and carries a CVSS score of 10.0. The company has published fix packs for each affected release, and no exploitation or public proof-of-concept has been confirmed.

    CVE-2026-93664 Deserialization Bug Enables Unauthenticated Takeover

    CVE-2026-93664 is a deserialization bug in the Station Launcher App. A deserialization flaw arises when an application reconstructs objects from untrusted input without adequate checks, and in this case the result is remote code execution that requires no authentication. The CVSS 10.0 rating is the maximum on the scale.

    The affected releases span 3DEXPERIENCE R2023x through R2026x. That range covers several years of the platform’s release history, so organizations that have not kept pace with upgrades may be running vulnerable versions.

    Two Command Injection Flaws at CVSS 9.9

    Two further flaws, CVE-2026-77033 and CVE-2026-19732, are OS command injection bugs rated CVSS 9.9. Unlike the deserialization flaw, they require a low-privileged account, so an attacker would first need some level of legitimate or stolen access.

    All three vulnerabilities carry a changed scope in their CVSS vectors. That designation means a successful exploit can affect resources beyond the component that contains the vulnerability, which raises the potential consequences compared with a flaw whose impact stays inside the vulnerable component.

    Dassault’s Disclosure and Fix Packs

    Dassault disclosed the flaws and published fix packs for each release line. The remediation is to apply the latest fix pack for the specific release in use. The company has not, in the material reviewed, described how the vulnerabilities were found or who reported them.

    No exploitation has been confirmed and no public proof-of-concept code is available. Those conditions describe the position at disclosure, and they do not prevent attackers from analyzing the fix packs to work out the flaws.

    Prior Dassault Entries in CISA’s Exploited Vulnerabilities List

    CISA added flaws in Dassault’s DELMIA Apriso product to its Known Exploited Vulnerabilities catalog in 2025. DELMIA Apriso is a separate product from 3DEXPERIENCE, and the earlier entries are not connected to the new flaws. They do show that Dassault software has attracted attacker attention before, which is context for how quickly defenders may need to act.

    What 3DEXPERIENCE’s Role Means for Exposure

    The 3DEXPERIENCE platform is used by engineering teams for design and manufacturing data. A takeover of a system in that environment could expose product designs and related engineering information, though the sources describe the risk in general terms and do not list specific data at risk.

    An unauthenticated remote code execution flaw is the most serious category for any network-reachable component, since it removes the need for credentials. Whether the Station Launcher App is typically exposed to the internet or confined to internal networks is not stated in the available reporting, and that detail would determine how many organizations face immediate remote risk.

    CVE-2026-93664 and 3DEXPERIENCE Patch Priority

    The difference between the unauthenticated flaw and the two low-privilege flaws affects how defenders sequence work. CVE-2026-93664 can be reached without any account, which is why it holds the top severity score. The two command injection bugs depend on an account existing, so their exposure grows if credentials are weak, shared or already compromised.

    Organizations running affected releases need to identify which release line they operate and obtain the matching fix pack, since Dassault issued separate packs per release. The advisory material does not give pack numbers, so customers must refer to Dassault’s own documentation for the correct file for R2023x, R2024x, R2025x or R2026x deployments.

    Related Posts