CVE-2025-53078: Samsung Electronics Data Management Server · Deserialization of Untrusted Data
Affects Samsung Electronics Data Management ServerSource CVE Database V5
Not known to be exploited · CVSS 8.0 High.
Data as of 26 Oct 2026, 12:55 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 29 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Samsung Electronics Data Management Server | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-53078 effectively, European organizations should: 1) Immediately inventory and identify any deployments of Samsung Electronics Data Management Server versions 2.0.0, 2.5.0.17, or 2.7.0.15 within their environments. 2) Restrict network access to the DMS to trusted management networks only, employing network segmentation and firewall rules to limit exposure. 3) Implement strict access controls and monitor for any privilege escalations or anomalous activities related to DMS processes. 4) Employ application-layer filtering or Web Application Firewalls (WAFs) that can detect and block suspicious serialized data payloads if feasible. 5) Engage with Samsung Electronics for updates or patches, and plan for rapid deployment once available. 6) Conduct thorough logging and monitoring of DMS logs and system events to detect early signs of exploitation attempts. 7) Consider deploying runtime application self-protection (RASP) or endpoint detection and response (EDR) solutions that can identify and block code execution anomalies. 8) Educate system administrators about the risks of deserialization vulnerabilities and the importance of applying principle of least privilege to service accounts running the DMS. These steps go beyond generic advice by focusing on network-level controls, monitoring, and vendor engagement specific to this product and vulnerability.
Description
Deserialization of Untrusted Data in Samsung DMS(Data Management Server) allows attackers to execute arbitrary code via write file to system