PatchTheCVErunning-elephant vulnerabilities
Recent CVEs affecting running-elephant products. 5 tracked.
running-elephant has 5 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 1. Most recent: 2026-02-17. Highest priority: CVE-2025-56819 (score 64/100).
- 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-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
FAQ
How do I fix running-elephant vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is running-elephant being exploited right now?
None of the tracked running-elephant CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which running-elephant CVE should I patch first?
CVE-2025-56819 currently ranks highest (64/100): An issue in Datart v.1.0.0-rc.3 allows a remote attacker to execute arbitrary code via the INIT connection par.