CVE-2025-56816: Datart 1.0.0-rc.3 is vulnerable to Directory Traversal

This month

HIGH 8.8DOWNGRADE

CVE-2025-56816 is a high-severity flaw (CVSS 8.8) affecting datart. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 b

Why this priority

High severity
Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	1.4% (top 29%)
CISA exploited list	No
Weakness	CWE-22, CWE-502
Published	2025-09-24
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: running-elephant

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-09-24 17:15 UTCPublished CVE record published
2026-06-17 09:42 UTCUpdated Record last modified

running-elephant datart DOWNGRADE

Affected: 1.0.0 rc3

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.0.0

1. Check installed version

apt-cache policy datart || rpm -q datart || datart --version

2. No fixed release: DOWNGRADE to a release before 1.0.0 (Debian / Ubuntu)

apt-cache madison datart sudo apt install datart=<VERSION_BEFORE_1.0.0> sudo apt-mark hold datart

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list datart sudo dnf downgrade datart-<VERSION_BEFORE_1.0.0> sudo dnf versionlock add datart

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-56816?

datart: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2025-56816 being exploited?

CVE-2025-56816 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-56816 affect?

CVE-2025-56816 affects datart. Severity is high (CVSS 8.8). 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 SnakeY

How urgent is CVE-2025-56816?

Priority 54/100. High severity; Public exploit reference

Related CVEs

CVE-2025-70829 MEDIUM 5.7 DOWNGRADE An information exposure vulnerability in Datart v1.0.0-rc.3 allows authenticated attackers to access sensitive
CVE-2025-70828 HIGH 8.8 DOWNGRADE An issue in Datart v1.0.0-rc.3 allows attackers to execute arbitrary code via the url parameter in the JDBC co
CVE-2025-56819 CRITICAL 9.8 DOWNGRADE An issue in Datart v.1.0.0-rc.3 allows a remote attacker to execute arbitrary code via the INIT connection par
CVE-2025-56815 HIGH 7.1 DOWNGRADE Datart 1.0.0-rc.3 is vulnerable to Directory Traversal in the POST /viz/image interface, since the server dire

References

← Back to latest CVEs