Loading vulnerability…
CVE-2026-40900 is a SQL injection vulnerability in DataEase, an open-source data visualization and analytics platform, affecting versions 2.10.20 and earlier. The flaw is in the /de2api/datasetData/previewSql endpoint, where user-supplied SQL is wrapped in a subquery without enforcing that the supplied input is limited to a single SELECT statement. When combined with the related JDBC blocklist bypass that permits allowMultiQueries=true, an attacker can escape the intended subquery context and execute arbitrary stacked SQL statements against the connected database. The issue enables execution of statements beyond read-only preview behavior, including UPDATE and other write operations.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
Repository is a self-contained PoC and Docker lab for a four-stage exploit chain against DataEase <= v2.10.20, culminating in root RCE via Quartz deserialization. Structure is small and focused: docker-compose.yml plus conf/ and mysql/ stand up a vulnerable DataEase + MySQL environment; exploit/de_common.py provides reusable HTTP/API helpers for /dekey key recovery, RSA-encrypted login, JWT forgery, datasource creation, and previewSql invocation; exploit/de_rce_chain.py is the main end-to-end exploit that authenticates, registers a malicious datasource with illegalParameters=[] and allowMultiQueries=true, generates a CommonsCollections6 gadget using ysoserial in a Java 8 Docker container, and injects stacked SQL queries to overwrite Quartz JOB_DATA and trigger deserialization; exploit/file_read.py demonstrates the arbitrary file-read stage by coercing DataEase to connect to a rogue MySQL server; exploit/rogue_mysql.py implements that minimal rogue MySQL server and captures uploaded file contents via LOCAL INFILE. The exploit is operational rather than framework-based: it contains working payload generation and execution logic, supports arbitrary commands and reverse shells, and includes all infrastructure needed for local reproduction.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A SQL injection vulnerability in the DataEase previewSql endpoint that, when chained, provides full read/write access to the application database.
A SQL injection vulnerability in DataEase versions 2.10.20 and below that allows an authenticated attacker with valid datasource credentials to execute stacked SQL statements and gain full read/write access to the connected database.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.