Threats / Dassault Systèmes / CVE-2025-6205
CVE-2025-6205
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Dassault Systèmes DELMIA Apriso vulnerability
Dassault Systèmes DELMIA Apriso contains a missing authorization vulnerability (CWE-862) allowing attackers to gain privileged access without proper permission checks.
Verdict
Today item — known-exploited.
An unauthenticated or low-privileged attacker can bypass authorization controls in DELMIA Apriso to escalate privileges and access restricted functionality. Active exploitation in the wild with high exploitability (EPSS 0.83) poses immediate risk to manufacturing operations.
CISA KEV Yes · 2025-10-285EPSS 0.71059 (verify live)6CVSS 9.13CISA SSVC Exploitation: active · Automatable: yes · Impact: total4Exploit Public PoC / detection · nuclei template13
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
138 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).
Probability (EPSS)
EPSS 0.71059 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.1 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N) · Affected: Dassault Systèmes, DELMIA Apriso. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-862 Missing Authorization — weakness family: Authorization / access control.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 85 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution 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 board1
Front door — unauthenticated access narrative 1
Attacker
I identify that the application fails to enforce authorization checks on sensitive operations.
Business
Unauthorized access to manufacturing execution systems disrupts production scheduling and quality control.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I escalate my privileges by directly accessing administrative functions without proper permission validation.
Business
Attackers gain control over critical process parameters, inventory management, and compliance records.
3
Lateral reach — past segmentation narrative 3
Attacker
I modify production workflows, alter audit logs, or extract sensitive operational data.
Business
Loss of data integrity, regulatory non-compliance, and inability to verify production authenticity damage customer trust and create legal liability.
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