Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore
Security NewsNews Explainer

Three Critical Station Launcher CVEs: Patch Scope and Checks

3DEXPERIENCE Station Launcher CVEs affect R2023x through R2026x. Identify deployments, confirm fixes with Dassault support, and verify running builds.

By
Brandefense Research Team
Reviewed by
Brandefense Analyst Team
Published
16 November 2026
Reading time
4 min read
Abstract enterprise software layers with three highlighted patch verification points.

The 3DEXPERIENCE Station Launcher CVEs disclosed on 16 November 2026 affect Station Launcher App across releases R2023x through R2026x. Dassault Systèmes rates all three critical. Identify affected deployments now; use the vulnerability intelligence platform alongside asset and patch records, then confirm the applicable remediation for each release through its linked support record, QA00000522688.

CVE-2026-93664 is the first triage priority because the vendor says it could permit unauthenticated remote code execution. CVE-2026-19732 and CVE-2026-77033 are command injection records that could permit arbitrary server commands. The published advisories do not name a fixed build, so an installed release number alone cannot prove remediation.

Advisory
Severity CriticalStatus Confirm Fix With Dassault
Station Launcher App CVEs
Confirm the corrected Station Launcher App build for each affected release through Dassault support record QA00000522688.
Published
2026-11-16 UTC
For
3DEXPERIENCE R2023x to R2026x Owners
Sharing
TLP:CLEAR

3DEXPERIENCE Station Launcher CVEs: Scope and Fix Check

Each advisory names Station Launcher App and the same R2023x through R2026x release span. The two command injection advisories use identical public descriptions. Treat them as separate CVE identifiers in inventory and support requests without assuming that their underlying code paths differ.

CVE Vendor description Affected release span Fix verification
CVE-2026-93664 Atlas record Untrusted deserialization; possible unauthenticated remote code execution R2023x to R2026x Confirm applicable corrected Station Launcher App build in QA00000522688
CVE-2026-19732 Atlas record OS command injection; possible arbitrary server commands R2023x to R2026x Confirm applicable corrected Station Launcher App build in QA00000522688
CVE-2026-77033 Atlas record OS command injection; possible arbitrary server commands R2023x to R2026x Confirm applicable corrected Station Launcher App build in QA00000522688

The linked Dassault support record QA00000522688 is the remediation route given by all three advisories. Its public landing page did not expose the release-specific fix details in this review. Ask your Dassault support contact which package, hotfix, or build closes each CVE for your deployment.

Which Deployment Should Be Patched First?

Start with Station Launcher App instances in the listed releases that can be reached from less trusted networks. The CVE-2026-93664 description explicitly names unauthenticated remote code execution. Its vendor-supplied CVSS 3.1 score is 10.0, while the other two records each score 9.9.

The CVSS 3.1 vectors for the command injection entries include low privileges, so inventory the accounts and paths that can reach those instances. NVD’s 16 November records provide no CVSS 4.0 score. These severity scores describe potential impact, not evidence that a particular deployment was attacked.

Brandefense Blackhole Keyword Matches
Exploit signals
  • CVE-2026-93664YesOne dark-chat post matched this CVE keyword.18 August to 16 November 2026
  • CVE-2026-19732YesOne dark-chat post matched this CVE keyword.18 August to 16 November 2026
  • CVE-2026-77033YesOne dark-chat post matched this CVE keyword.18 August to 16 November 2026
Verdict Unverified Mentions

These are posts per keyword, and the three counts may overlap; do not add them as unique posts. The mentions do not verify an incident or active exploitation.

For a repeatable triage process, compare your asset and patch records with the confirmed vendor guidance. Use the vulnerability management guide to assign owners and track exceptions. This workflow is our defensive recommendation, not a vendor instruction.

What Should Owners Verify After the Change?

List every affected 3DEXPERIENCE deployment, its Station Launcher App build, release branch, exposure route, and owner. Compare each entry with the applicable support guidance before scheduling remediation. If a fix is delayed, restrict untrusted reachability.

Station Launcher response order
  • Inventory each deploymentRecord the release, launcher build, reachability, and owner.
  • Confirm the fixMatch every CVE and release to QA00000522688 or Dassault support guidance.
  • Apply the changePatch affected launcher instances, prioritizing externally reachable systems.
  • Verify the resultRecheck the installed build and preserve the support confirmation.
  • Review evidenceExamine relevant application, server, and process logs if exposure warrants investigation.

After patching, record the running build rather than only the installer version or change ticket. For any suspicious period, preserve application and server logs and review unexpected process activity. The remote code execution glossary explains why server-side activity matters when scoping a suspected compromise.

Keep the three CVE identifiers distinct in remediation evidence and support correspondence. Recheck the vendor advisories if the release-specific fix information changes. A completed deployment record should show the affected branch, the corrected build confirmed by support, and the date it was verified.

Frequently Asked Questions

Which Station Launcher App releases need review?

Dassault Systèmes lists 3DEXPERIENCE releases R2023x through R2026x for all three CVEs. Inventory the installed app build in each deployment and check the applicable support guidance.

Can administrators use the published CVE pages to identify a fixed build?

The public advisories give the affected release span but no corrected build number. Confirm the release-specific remediation in Dassault support record QA00000522688 or with its support team.

Why should CVE-2026-93664 be triaged first?

Its vendor description says unauthenticated remote code execution could result. Prioritize reachable affected deployments, then address the two command injection entries and verify each fix.

Sources

  1. Dassault Systèmes: CVE-2026-93664 advisory
  2. Dassault Systèmes: CVE-2026-19732 advisory
  3. Dassault Systèmes: CVE-2026-77033 advisory
  4. NVD: CVE-2026-93664
  5. NVD: CVE-2026-19732
  6. NVD: CVE-2026-77033
Share this articleLinkedInXEmail
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →