CVE-2025-64428: dataease · Injection
Affects dataeaseSource GCVE Database
Public exploit available · CVSS 8.9 High : upgrade to 2.10.17 as a priority.
Data as of 13 Nov 2026, 18:46 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 8.9 |
|---|
- Patch
- Available – fixed in 2.10.17
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Upgrade dataease/dataease to 2.10.17.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubdataease/dataeasepkg:github/dataease/dataeaseOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Dataease to version 2.10.17 or later, where the vulnerability is fully fixed. Versions prior to 2.10.17 remain vulnerable despite partial blacklist mitigations introduced in 2.10.14. No other mitigations are noted in the vendor advisory.
Description
Dataease versions prior to 2.10.17 are affected by a JNDI injection vulnerability (CWE-74). Although a blacklist was introduced in version 2.10.14, injection remains possible through specific URI schemes (iiop, corbaname, iiopname). This flaw allows remote attackers to perform injection attacks without authentication. The issue has been fixed in version 2.10.17.