# CVE-2026-40899: DataEase has an Arbitrary File Read Vulnerability

> An authenticated attacker can bypass JDBC blocklists to read arbitrary files from the server filesystem via a rogue MySQL connection.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Apr 2026
- **Updated:** 18 Apr 2026
- **Also known as:** GHSA-944x-93jf-h3rx

## What is CVE-2026-40899?

CVE-2026-40899 is a high-severity path traversal vulnerability in Dataease Dataease, published on 16 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

DataEase is an open-source data visualization and analytics platform. Versions 2.10.20 and below contain a JDBC parameter blocklist bypass vulnerability in the MySQL datasource configuration. The Mysql class uses Lombok's @Data annotation, which auto-generates a public setter for the illegalParameters field that contains the JDBC security blocklist. When a datasource configuration is submitted as JSON, Jackson deserialization calls setIllegalParameters with an attacker-supplied empty list, replacing the blocklist before getJdbc() validation runs. This allows an authenticated attacker to include dangerous JDBC parameters such as allowLoadLocalInfile=true, and by pointing the datasource at a rogue MySQL server, exploit the LOAD DATA LOCAL INFILE protocol feature to read arbitrary files from the DataEase server filesystem, including sensitive environment variables and database credentials. This issue has been fixed in version 2.10.21.

Weakness: CWE-183 (Permissive List of Allowed Inputs)

## Which versions are affected by CVE-2026-40899?

It affects 1 product.


Products: Dataease Dataease.

## How do I fix CVE-2026-40899?

No fix has been published for CVE-2026-40899 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-40899 being exploited?

There is no known exploitation of CVE-2026-40899 in the wild and no public exploit code.

## Other vulnerabilities in Dataease Dataease

- [CVE-2024-57707](https://insights.sbomify.com/CVE-2024-57707/): Code injection in n/a (critical 9.8)
- [CVE-2024-46997](https://insights.sbomify.com/CVE-2024-46997/): DataEase's H2 datasource has a remote command execution risk (critical 9.8)
- [CVE-2023-33963](https://insights.sbomify.com/CVE-2023-33963/): DataEase data source has deserialization vulnerability (critical 9.8)
- [CVE-2023-28437](https://insights.sbomify.com/CVE-2023-28437/): SQL injection vulnerability due to the keyword blacklist for defending against SQL injection will be bypassed (critical 9.8)
- [CVE-2022-39312](https://insights.sbomify.com/CVE-2022-39312/): Dataease Mysql Data Source JDBC Connection Parameters Not Verified Leads to Deserialization Vulnerability (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-40899 and fix it if it is affected.

What it is: CVE-2026-40899 is a high-severity path traversal vulnerability in Dataease Dataease, published on 16 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-40899 in the wild and no public exploit code.

Affected product: Dataease Dataease. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-40899/ (Markdown: https://insights.sbomify.com/CVE-2026-40899/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-40899
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-40899
- OSV: https://osv.dev/vulnerability/CVE-2026-40899

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-40899/
Summaries are generated and may contain mistakes; the official description above is the record.