CVE-2025-48998 Dataease MYSQL JDBC File Reading Vulnerability
Authenticated attackers can read and deserialize arbitrary files via JDBC connections, potentially leading to code execution in DataEase.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-48998?
CVE-2025-48998 is a high-severity unsafe deserialization vulnerability in Dataease Dataease, published on 3 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
DataEase is an open source business intelligence and data visualization tool. Prior to version 2.10.6, a bypass of the patch for CVE-2025-27103 allows authenticated users to read and deserialize arbitrary files through the background JDBC connection. The vulnerability has been fixed in v2.10.10. No known workarounds are available.
Which versions are affected by CVE-2025-48998?
It affects 1 product.
Products include Dataease Dataease.
How do I fix CVE-2025-48998?
No fix has been published for CVE-2025-48998 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-48998 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-48998 exists.
Other vulnerabilities in Dataease Dataease
- CVE-2024-57707 Code injection in n/a
- CVE-2024-46997 DataEase's H2 datasource has a remote command execution risk
- CVE-2023-33963 DataEase data source has deserialization vulnerability
- CVE-2023-28437 SQL injection vulnerability due to the keyword blacklist for defending against SQL injection will be bypassed
- CVE-2022-39312 Dataease Mysql Data Source JDBC Connection Parameters Not Verified Leads to Deserialization Vulnerability