CVE-2026-50124
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDataEase is an open source data visualization and analysis tool. Prior to 2.10.23, DataEase can be exploited by uploading payload.zip through the Excel upload API /datasource/upload, creating an H2 datasource that uses the zip: protocol, and executing an SQL dataset path where CalciteProvider.jdbcFetchResultField calls statement.executeQuery(), causing precompiled Java aliases in test.mv.db to execute arbitrary code. This issue is fixed in version 2.10.23.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn DataEase versions prior to 2.10.23, an attacker can upload a malicious Excel file (payload.zip) via the /datasource/upload API that creates an H2 datasource using the zip: protocol. The vulnerability in CalciteProvider.jdbcFetchResultField allows execution of precompiled Java aliases in test.mv.db, enabling arbitrary code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check DataEase versionAccess the DataEase admin interface or check the installed version via the API (e.g., /api/version endpoint or docker image tag). Compare against 2.10.23.Affected if Installed version is prior to 2.10.23 (e.g., 2.10.0, 2.9.x, etc.)
-
Verify /datasource/upload API accessibilityReview API access controls, authentication settings, and web server logs for requests to /datasource/upload endpoint. Check if the endpoint is publicly accessible without proper authorization.Affected if The /datasource/upload API is exposed without authentication or to untrusted users
-
Inspect H2 datasource configurationsAccess DataEase datasource settings and review all configured H2 datasources. Look for any datasources using the zip: protocol in their connection string (e.g., zip:/path/to/file).Affected if Any H2 datasource configuration uses the zip: protocol in its connection URL
-
Examine test.mv.db for custom Java aliasesLocate the test.mv.db file in the DataEase data directory. Inspect its contents for custom Java aliases or precompiled classes that may have been added via the malicious upload.Affected if test.mv.db contains unexpected or custom Java alias definitions not created by administrators
A user is affected if running DataEase version prior to 2.10.23 AND the /datasource/upload API is accessible to untrusted parties, resulting in potential zip: protocol H2 datasources or malicious Java aliases in test.mv.db.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade DataEase to version 2.10.23 or later. Until then, restrict access to the /datasource/upload API and monitor for suspicious zip: protocol usage in datasource configurations.
DataEase 2.10.23
- 1. Back up your current DataEase installation and all databases.
- 2. Download DataEase version 2.10.23 or later from the official GitHub releases page (github.com/dataease/dataease).
- 3. Stop the running DataEase service.
- 4. Install version 2.10.23 following the standard upgrade procedure for your deployment method.
- 5. Restart the DataEase service.
- 6. Verify the upgrade was successful by checking the version number in the admin panel or via API.
- 7. Ensure the /datasource/upload endpoint now properly validates uploaded files and rejects malicious payloads.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50124 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-50124 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data