CVE-2025-5086
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA deserialization of untrusted data vulnerability affecting DELMIA Apriso from Release 2020 through Release 2025 could lead to a remote code execution.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA deserialization vulnerability in DELMIA Apriso allows attackers to deserialize untrusted data, potentially executing arbitrary code remotely. The flaw affects versions from Release 2020 through Release 2025, spanning five years of releases.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2020, <= 2025CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed DELMIA Apriso versionCheck the application version through the Windows installed programs list, or query the DELMIA Apriso installation directory for version information. Common locations include the installation root folder or registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\DassaultSystemes\DELMIA Apriso.Affected if The installed version falls within the range of Release 2020 through Release 2025 inclusive.
-
Determine if Apriso server services are runningOpen Windows Services management console (services.msc) and look for DELMIA Apriso-related services, or use command 'sc query' to enumerate running services. Note which Apriso services are started and their startup type.Affected if Any DELMIA Apriso services are running and listening on network ports.
-
Identify deserialization endpointsReview the Apriso configuration files (typically found in the installation directory under config or etc folders) for exposed endpoints, remoting services, or web service configurations that handle serialized data. Check for RMI, JMX, SOAP, or similar remoting interfaces.Affected if Deserialization endpoints or remoting services are enabled and accessible without authentication.
-
Check network exposure of Apriso portsUse netstat or PowerShell Get-NetTCPConnection to identify ports listening on Apriso services. Review firewall rules to determine if these ports are exposed to untrusted networks.Affected if Apriso services are listening on ports accessible from untrusted network segments or the internet.
-
Review application deserialization configurationExamine the Apriso configuration files for settings related to object deserialization, Java serialization, or custom serialization handlers. Look for patterns like 'deserialize', 'objectinputstream', or similar in configuration XML or properties files.Affected if Unsafe deserialization handlers are enabled in the configuration without additional validation layers.
A user is affected if they have DELMIA Apriso Release 2020-2025 installed with deserialization endpoints exposed to the network.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor-supplied patch or upgrade to a patched release version. If immediate patching is not possible, restrict network access to vulnerable endpoints and monitor for exploitation attempts.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5086 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-5086 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data