CVE-2025-6204
Published: October 28, 2025
Official Description
Dassault Systèmes DELMIA Apriso contains a code injection vulnerability that could allow an attacker to execute arbitrary code.
CISA KEV Advisory
Dassault Systèmes DELMIA Apriso Code Injection Vulnerability
Dassault Systèmes DELMIA Apriso contains a code injection vulnerability that could allow an attacker to execute arbitrary code.
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Risk Analysis
Dassault Systèmes DELMIA Apriso is affected by a code injection vulnerability that could allow an attacker to execute arbitrary code. Its presence in CISA's KEV catalog and active exploitation in the wild make this a high-severity issue. The high EPSS score further indicates a significant likelihood of exploitation.
This vulnerability is actively being exploited in the wild and is listed in CISA's Known Exploited Vulnerabilities catalog. It allows for arbitrary code execution through code injection.
Apply all available security updates and patches for Dassault Systèmes DELMIA Apriso. Implement secure coding practices and ensure proper input validation to prevent code injection attacks.
Technical Analysis
CVE-2025-6204 requires local access, meaning attackers must already have a foothold on the target system.
Exploitation requires some privileges, which limits the exposure to scenarios where an attacker has already gained initial access.
CISA has added CVE-2025-6204 to the Known Exploited Vulnerabilities (KEV) catalog, confirming active exploitation in the wild. U.S. federal agencies are required to patch this within the mandated timeframe, and all organizations should treat remediation as urgent.
Exploit & PoC Resources
All References (2)
Quick Facts
Recommended Actions
- →Apply vendor patches immediately
- →Monitor CVE-2025-6204 in threat intel feeds
- →Review IDS/IPS signatures for exploitation attempts
- !CISA KEV: Federal agencies must patch per BOD 22-01 timeline
- !Active exploitation confirmed — treat as P1