Loading vulnerability…
CVE-2026-23958 affects DataEase, an open-source data visualization and analysis platform. In DataEase versions prior to 2.10.19, the application derives the JWT signing secret deterministically from the MD5 hash of the user's password. Because the signing secret is directly tied to password material and is therefore predictable for a given account, an attacker can use API endpoints that verify JWT tokens as an oracle to brute-force the administrator's password and validate guesses. This weak credential handling undermines the integrity of token-based authentication and can enable authentication bypass against privileged accounts.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical authentication bypass vulnerability in DataEase that serves as the starting point of a credential-less exploit chain.
A vulnerability in DataEase (prior to v2.10.19) where JWT signing secrets are deterministically derived from the MD5 hash of a user password, enabling offline/online brute-force of the admin password via JWT verification endpoints.
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.