CVE-2025-56816 Deserialization in n/a
Attackers can achieve remote code execution by uploading malicious YAML files that trigger unsafe deserialization in Datart.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2025-56816?
CVE-2025-56816 is a high-severity unsafe deserialization vulnerability in n/a, published on 24 Sep 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
Datart 1.0.0-rc.3 is vulnerable to Directory Traversal. The configuration file handling of the application allows attackers to upload arbitrary YAML files to the config/jdbc-driver-ext.yml path. The application parses this file using SnakeYAML's unsafe load() or loadAs() method without input sanitization. This allows deserialization of attacker-controlled YAML content, leading to arbitrary class instantiation. Under certain conditions, this can be exploited to achieve remote code execution (RCE).
Which versions are affected by CVE-2025-56816?
It affects 1 product.
Products include Running-Elephant Datart.
How do I fix CVE-2025-56816?
No fix has been published for CVE-2025-56816 yet. Limit exposure of the affected software until one is available.
Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.
Is CVE-2025-56816 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56816 exists.
Other vulnerabilities in n/a
Sources
Also known as GHSA-pqpp-98pw-x43g.