Cyber Resilience

CVE-2026-40899

Dataease ≤ 2.10.21

Public PoC
Published
16 April 2026
Modified
20 April 2026
CVSS Score v4 8.3
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/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
EPSS Score 0.0039 32th percentile
Risk Priority 38 floored blend · peak EPSS

Summary

CVE-2026-40899 is a high-severity Permissive List of Allowed Inputs (CWE-183) vulnerability in Dataease Dataease. Its CVSS base score is 8.3 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 32th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A06:2025 Insecure Design

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)
CWE-183

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-37258Same product: Dataease Dataease
CVE-2026-33082Same product: Dataease Dataease
CVE-2026-33122Same product: Dataease Dataease
CVE-2026-40900Same product: Dataease Dataease
CVE-2025-64163Same product: Dataease Dataease
CVE-2026-33121Same product: Dataease Dataease
CVE-2026-32140Same product: Dataease Dataease
CVE-2026-33207Same product: Dataease Dataease
CVE-2025-62422Same product: Dataease Dataease
CVE-2025-58045Same product: Dataease Dataease

Affected Assets

dataease
dataease
≤ 2.10.21

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.5.2
  • V4.4.2

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

Strict validity checks on inputs directly stop overly permissive allow lists from being used as the protection mechanism.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require rigorous allow-list design and testing that prevents permissive input validation.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect overly broad allow-lists, but does not inherently prevent their creation.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate strict, minimal allow-lists and input validation rules that prevent overly permissive lists.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture and engineering principles require explicit, least-privilege input validation designs that directly address permissive allow-lists.

A.8.28 Secure coding partial match
prevents

Secure coding standards enforce rigorous input validation and reject unsafe values, mitigating permissive allow-list weaknesses.

A.8.9 Configuration management none match
none

Configuration management can enforce validated input rules, yet does not directly address the design flaw of permissive lists.

References