CVE-2025-70829: An information exposure vulnerability in Datart v1.0.0-rc.3 allows authenticated attackers to access sensitive

Routine

MEDIUM 5.7DOWNGRADE

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

An information exposure vulnerability in Datart v1.0.0-rc.3 allows authenticated attackers to access sensitive data via a custom H2 JDBC connection string.

Why this priority

Public exploit reference

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

Risk facts

CVSS score	5.7 (Medium)
Attack vector	Adjacent network
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.5% (top 59%)
CISA exploited list	No
Weakness	CWE-200
Published	2026-02-17
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

2026-02-17 15:16 UTCPublished CVE record published
2026-06-17 10:03 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-70829?

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

Is CVE-2025-70829 being exploited?

CVE-2025-70829 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-70829 affect?

CVE-2025-70829 affects datart. Severity is medium (CVSS 5.7). An information exposure vulnerability in Datart v1.0.0-rc.3 allows authenticated attackers to access sensitive data via a custom H2 JDBC connection string.

How urgent is CVE-2025-70829?

Priority 35/100. Public exploit reference

Related CVEs

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-56816 HIGH 8.8 DOWNGRADE Datart 1.0.0-rc.3 is vulnerable to Directory Traversal
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