basicsecurity.net
Proof, not just disclosure.
Threats / Dassault Systèmes / CVE-2025-6204
CVE-2025-6204 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Dassault Systèmes DELMIA Apriso vulnerability

Dassault Systèmes DELMIA Apriso contains a code injection vulnerability (CWE-94) allowing arbitrary code execution. The vulnerability is actively exploited in the wild.

Verdict

Today item — known-exploited.

A code injection flaw in DELMIA Apriso enables remote arbitrary code execution. Active exploitation in the wild presents immediate risk to manufacturing and operations environments relying on this platform.

CISA KEV Yes · 2025-10-283EPSS 0.75306 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
3 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-10-28).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.75306 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Dassault Systèmes, DELMIA Apriso. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-94 Code Injection — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-94 · Code InjectionInjection
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I craft malicious input containing executable code and submit it to a DELMIA Apriso interface or API endpoint.
Business
Attackers gain code execution within the manufacturing operations platform, compromising production systems and data integrity.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I execute arbitrary commands with the privileges of the DELMIA Apriso application process.
Business
Operational technology systems become compromised, enabling disruption of manufacturing workflows and potential theft of proprietary designs or production data.
3

Lateral reach — past segmentation narrative 3

Attacker
I establish persistence and lateral movement within the enterprise network from the compromised Apriso instance.
Business
The breach expands beyond manufacturing systems to critical business infrastructure, increasing exposure and recovery costs.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 3 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by 3DS (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by 3DSCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.